fast-uri
Affected
- introduced
2.4.1, fixed2.4.5(semver)
Fixed versions
2.4.5
Fix
- Fixed version
2.4.5npm install [email protected]
Advisory
Also known as: CVE-2026-75899
fast-uri vulnerable to server-side request forgery via repeated hostname percent-decoding
Impact
fast-uri decodes a hostname's percent escapes twice in a single normalize() or resolve() call: once during parsing and again during authority recomposition. A nested percent-encoded host therefore survives the first decode and is turned into a live destination by the second, so normalize('http://%256c%256f%2563%2561%256c%2568%256f%2573%2574/') returns http://localhost/. Applications that normalize or resolve an untrusted URI before an SSRF check, redirect validation, or host allowlist can be steered to a different destination, including internal addresses such as loopback or a cloud metadata endpoint, than the encoded input appeared to contain. This is an incomplete-fix variant of CVE-2026-6322, whose encoded-authority-delimiter fix introduced the second decode.
Patches
Fixed in fast-uri 2.4.5, 3.1.6, and 4.1.3.
Workarounds
Reject untrusted URIs whose host component contains an encoded percent sign (%25) before passing them to normalize() or resolve().
High Basis: The source's own band: HIGH
2.4.1, fixed 2.4.5 (semver)2.4.5
2.4.5npm install [email protected]3.1.2, fixed 3.1.6 (semver)3.1.6
3.1.6npm install [email protected]4.0.0, fixed 4.1.3 (semver)4.1.3
4.1.3npm 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