fast-uri
Affected
- introduced
2.3.1, fixed2.4.3(semver)
Fixed versions
2.4.3
Fix
- Fixed version
2.4.3npm install [email protected]
Advisory
Also known as: CVE-2026-16221
fast-uri vulnerable to host confusion via literal backslash authority delimiter
Impact
fast-uri v4.1.0 and earlier do not treat a literal backslash (U+005C) as an authority delimiter. Node's native WHATWG URL (used by fetch(), undici, and Node's http/https clients) normalizes \ to / for special schemes (http, https, ws, wss, ftp, file), so the two parsers extract different hosts from the same input string.
For example, http://evil.com\@allowed.com is treated by fast-uri as host allowed.com with userinfo evil.com\, while Node's WHATWG URL parser and fetch() see host evil.com with path /@allowed.com.
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, including cloud metadata endpoints, loopback, or internal hosts.
Patches
Upgrade to fast-uri v4.1.1, v3.1.4, or v2.4.3.
Workarounds
None. Upgrade to the patched version.
High Basis: The source's own band: HIGH
2.3.1, fixed 2.4.3 (semver)2.4.3
2.4.3npm install [email protected]3.0.0, fixed 3.1.4 (semver)3.1.4
3.1.4npm install [email protected]4.0.0, fixed 4.1.1 (semver)4.1.1
4.1.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0