Packages / fast-uri / Security
fast-uri vulnerable to host confusion via skipped IDN canonicalization on scheme-relative references
Affected releases · fast-uri
- 4.x4.0.1 – 4.1.2Fixed in 4.1.3
- 3.x3.1.3 – 3.1.5Fixed in 3.1.6
- 2.x2.4.2 – 2.4.4Fixed in 2.4.5
On 4.x, the newest line:
npm install fast-uri@4.1.3Every release on a timeline
Not affected
4.0.0
1 release
Affected
4.0.1 – 4.1.2
4 releases
Fixed
4.1.3 – 4.2.3
7 releases, latest
Not affected
3.0.0 – 3.1.2
10 releases
Affected
3.1.3 – 3.1.5
3 releases
Fixed
3.1.6 – 3.1.9
4 releases
Not affected
2.0.0 – 2.4.1
7 releases
Affected
2.4.2 – 2.4.4
3 releases
Fixed
2.4.5 – 2.4.8
4 releases
What happens
Impact
fast-uri canonicalizes a host to its ASCII form only when the input carries an explicit scheme. When resolve() resolves a scheme-relative reference (//host/) against a scheme-bearing base, it still emits the host verbatim even though the effective scheme is known, so re-parsing the resolved URI yields a different host than the one resolve() returned. An application that resolves an untrusted reference with fast-uri and then checks or routes on the resulting host can make a policy decision on one host and reach another. This is an incomplete-fix variant of CVE-2026-13676, whose IDN canonicalization was applied only to the scheme-bearing form.
Patches
Upgrade to fast-uri 2.4.5, 3.1.6, or 4.1.3. resolve() now canonicalizes the host once the effective scheme is known, and fails closed if a raw non-ASCII host cannot be converted.
Workarounds
Resolve scheme-relative references against a base that carries a scheme before performing any host-policy or origin check.
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.