fast-uri
Affected
- introduced
4.0.0, fixed4.0.1(semver)
Fixed versions
4.0.1
Fix
- Fixed version
4.0.1npm install [email protected]
Advisory
Also known as: CVE-2026-13676
fast-uri vulnerable to host confusion via failed IDN canonicalization
Impact
fast-uri versions >= 2.3.1, <= 4.0.0 fail to canonicalize Unicode/IDN hostnames for HTTP-family URLs. The IDN conversion path calls URL.domainToASCII(...) on the global WHATWG URL constructor, where that helper does not exist. The resulting TypeError is silently routed into parsed.error, but parse(), normalize(), and equal() all return with the host left in its original Unicode form.
For example, http://127。0。0。1/ is treated by fast-uri as host 127。0。0。1, while Node's WHATWG URL parser and fetch() canonicalize the same input to 127.0.0.1.
Applications that use fast-uri to enforce host-based policy (denylists, loopback 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.0.1, v3.1.3, or v2.4.2
Workarounds
None. Upgrade to the patched version.
High Basis: The source's own band: HIGH
4.0.0, fixed 4.0.1 (semver)4.0.1
4.0.1npm install [email protected]3.0.0, fixed 3.1.3 (semver)3.1.3
3.1.3npm install [email protected]2.3.1, fixed 2.4.2 (semver)2.4.2
2.4.2npm 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