CVE-2026-75931: fast-uri vulnerable to host confusion via skipped IDN canonicalization on scheme-relative references

Published Aug 24, 2026
·
Updated

fast-uri is a URI parser for Node.js. It canonicalizes a host to its ASCII form only when the input carries an explicit scheme, so a scheme-relative reference such as a host preceded by two slashes is returned with its host verbatim and no error set. As a result fast-uri's own entry points disagree with each other: parse, resolve, normalize, and equal can yield different hosts for the same input depending only on whether a scheme is written out, and equal can return opposite verdicts for the same pair of hosts. An application that extracts a host with fast-uri to check it against a policy list and then resolves the same reference can make its decision on one host while the destination is another, enabling host confusion and policy bypass. The affected versions are 2.4.2 up to but not including 2.4.5, 3.1.3 up to but not including 3.1.6, and 4.0.1 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which canonicalize the host consistently across the resolve path. Users should upgrade to a patched version.

Affected Software

1 affected component
npm/fast-uri>2.4.2<2.4.5, >3.1.3<3.1.6, >4.0.1<4.1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade fast-uri to a version that resolves this vulnerability.

    Fixed in 2.4.5
  2. Upgrade

    Upgrade fast-uri to a version that resolves this vulnerability.

    Fixed in 3.1.6
  3. Upgrade

    Upgrade fast-uri to a version that resolves this vulnerability.

    Fixed in 4.1.3

Event History

Aug 24, 2026
CVE Published
via MITRE·09:30 AM
Data Sourced
via MITRE·09:30 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments using npm/fast-uri versions 2.4.2 through 2.4.4, 3.1.3 through 3.1.5, or 4.0.1 through 4.1.2 are affected. The issue is fixed in versions 2.4.5, 3.1.6, and 4.1.3.

2

What application behavior makes this vulnerability exploitable?

An application is exposed when it uses fast-uri to extract a host for comparison against a policy or allowlist and then resolves the same scheme-relative reference. The host used for the policy decision can differ from the resolved destination because scheme-relative references skip IDN canonicalization.

3

Does exploitation require authentication or user interaction?

No. The supplied severity vector indicates network attack access, low attack complexity, no privileges required, and no user interaction required.

4

What should teams do if they cannot immediately upgrade?

The provided remediation is to upgrade to a patched fast-uri release. No temporary mitigation or configuration workaround is specified in the available data.

5

How can teams determine whether they are at risk?

Check the installed fast-uri version and identify code paths that validate hosts with fast-uri before resolving scheme-relative references. In affected versions, parse, resolve, normalize, and equal may produce inconsistent host handling for inputs beginning with two slashes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203