All vulnerabilities

npm

CVE-2026-18446

fast-uri vulnerable to host confusion via backslash authority introducer

Severity
High 7.5
Published
3 Aug 2026
Last changed
10 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
2.4.4, 3.1.5, 4.1.2
Exploit chance
0.4% in the next 30 daysHigher than 32% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-436
Attack
Over the network · No login needed · No user action needed
Attacker can
Change data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Also known as
GHSA-7p8r-x3mc-p8w7
Sources
OSV.dev and GitHub

Description

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…

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Workarounds

None. Upgrade to the patched version.

Workarounds as given by the GitHub Advisory Database, CC BY 4.0.

Affected software

SoftwareAffected versions
fast-urinpm · osv:npm:fast-uri
  • Every version before 2.4.4
  • From 3.0.0 before 3.1.5
  • From 4.0.0 before 4.1.2

About fast-uri

Weekly downloads (npm)
227,816,128npm, 17 Nov 2026

References