fast-uri
Affected
- introduced
0, fixed2.4.8(semver)
Fixed versions
2.4.8
Fix
- Fixed version
2.4.8npm install [email protected]
Advisory
Also known as: CVE-2026-110095
fast-uri vulnerable to improper path equivalence in relative reference normalization
Impact
fast-uri's normalize() and serialize() apply RFC 3986 dot-segment removal (remove_dot_segments) to the path of a relative-path reference. RFC 3986 section 5.2.4 defines that algorithm only for the merged target path during resolution, not for the reference itself, so applied to the reference it drops leading .. segments and can turn a document-relative reference into a root-relative one.
For example, normalize('a/../b') returns /b and normalize('../x') returns x, so resolve(base, normalize(ref)) points at a different resource than resolve(base, ref), and equal() treats distinct references as the same.
Applications that normalize attacker-supplied or user-supplied relative references and then resolve them, or use them as cache, deduplication, or authorization keys, can have a reference escape its intended directory and point at a different resource.
Patches
Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.
Workarounds
Do not normalize a relative reference before resolving it. Resolve it against the absolute base first, then normalize the absolute result.
Low Basis: The source's own band: LOW
0, fixed 2.4.8 (semver)2.4.8
2.4.8npm install [email protected]3.0.0, fixed 3.1.9 (semver)3.1.9
3.1.9npm install [email protected]4.0.0, fixed 4.2.3 (semver)4.2.3
4.2.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