En bref
- CVE-2026-75931 est une vulnérabilité ÉLEVÉE (CVSS 7.5) touchant fast-uri (openjsf), fast-uri.
- Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.40%, plus élevée que 34.0% des vulnérabilités.
- Correctif : mettre à jour vers 2.4.5, 3.1.6, 4.1.3 ou plus récent.
| Package | Affected versions | Patched versions |
|---|
| fast-uri | ≥ 2.4.2, < 2.4.5≥ 3.1.3, < 3.1.6≥ 4.0.1, < 4.1.3
| 2.4.53.1.64.1.3
|
| fast-uri npm | ≥ 2.4.2, < 2.4.5≥ 3.1.3, < 3.1.6≥ 4.0.1, < 4.1.3
| 2.4.53.1.64.1.3
|
Description
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.
NVD description
fast-uri is a URI parser for Node.js. It canonicalizes a host to its ASCII form only when the input carries an explicit scheme, so a scheme-relative reference such as a host preceded by two slashes is returned with its host verbatim and no error set. As a result fast-uri's own entry points disagree with each other: parse, resolve, normalize, and equal can yield different hosts for the same input depending only on whether a scheme is written out, and equal can return opposite verdicts for the same pair of hosts. An application that extracts a host with fast-uri to check it against a policy list and then resolves the same reference can make its decision on one host while the destination is another, enabling host confusion and policy bypass. The affected versions are 2.4.2 up to but not including 2.4.5, 3.1.3 up to but not including 3.1.6, and 4.0.1 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which canonicalize the host consistently across the resolve path. Users should upgrade to a patched version.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free