Packages / fast-uri / Security

HighVulnerabilityGHSA-7p8r-x3mc-p8w7CVE-2026-18446Published 3 Aug 2026

fast-uri vulnerable to host confusion via backslash authority introducer

Your version

Affected releases · fast-uri

  • 4.x4.0.0 – 4.1.1Fixed in 4.1.2
  • 3.x3.0.0 – 3.1.4Fixed in 3.1.5
  • 2.x2.0.0 – 2.4.3Fixed in 2.4.4
  • 1.x and older0.0.1 – 1.0.1No fix, no longer updated

On 4.x, the newest line:

npm install fast-uri@4.1.2
Every release on a timeline
4.x
  1. Affected

    4.0.0 – 4.1.1

    4 releases

  2. Fixed

    4.1.2 – 4.2.3

    8 releases, latest

3.x
  1. Affected

    3.0.0 – 3.1.4

    12 releases

  2. Fixed

    3.1.5 – 3.1.9

    5 releases

2.x
  1. Affected

    2.0.0 – 2.4.3

    9 releases

  2. Fixed

    2.4.4 – 2.4.8

    5 releases

1.x
  1. Affected

    1.0.0 – 1.0.1

    2 releases

0.x
  1. Affected

    0.0.1 – 0.0.2

    2 releases

47 stable releases of fast-uri, oldest to newest, one row per major.

What happens

Impact

fast-uri v4.1.1 and earlier require a literal // to recognize a URI authority, so a reference that uses \\, /\, or \/ as the authority introducer (in place of //, after an optional scheme) is parsed with no authority: the sequence and everything after it fold into the path. Node's native WHATWG URL (used by fetch(), undici, and Node's http/https clients) instead treats \ as interchangeable with / for special schemes (http, https, ws, wss, ftp, file), so the two parsers extract different hosts from the same input.

For example, fast-uri resolves \\evil.com/path against base https://allowed.com/ to https://allowed.com/%5C%5Cevil.com/path (confined to the trusted host), while Node's WHATWG URL resolves the same reference to https://evil.com/path.

Applications that use fast-uri to enforce host-based policy (allowlists, denylists, loopback/SSRF filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL or fetch() consumers see a policy/use desync and can be steered to an unintended destination.

Patches

Upgrade to fast-uri v4.1.2, v3.1.5, v2.4.4.

Workarounds

None. Upgrade to the patched version.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.