CVE-2026-13676
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Summary
fast-uri versions 2.3.1 through 3.1.2 and 4.0.0 fail to canonicalize Unicode (IDN) hostnames for HTTP-family URLs. The IDN conversion path calls a helper that does not exist on the global URL constructor, silently leaving the host in its original Unicode form while normalize() and equal() still return values that differ from a WHATWG-compatible URL parser. Applications that use fast-uri to enforce host-based policy (denylists, loopback filtering, redirect validation, outbound proxy routing) before passing the same URL to Node's URL or fetch can be bypassed when the two implementations resolve the same input to different hosts. Patches: upgrade to fast-uri 3.1.3 for the 3.x line or 4.0.1 for the 4.x line. Workarounds: enforce host policy using the same URL parser used for the actual request, or reject non-ASCII hosts before policy checks.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| fast-uri | fast-uri | 4.0.0 < 4.0.1 | affected |
| fast-uri | fast-uri | 4.0.1 | unaffected |
| fast-uri | fast-uri | 2.3.1 < 3.1.3 | affected |
| fast-uri | fast-uri | 3.1.3 | unaffected |
Weaknesses
- CWE-436: CWE-436: Interpretation Conflict
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: yes
- Technical Impact: partial
fast-uri: fast-uri: Security policy bypass due to improper Unicode hostname canonicalization
Additional References
- https://access.redhat.com/security/cve/CVE-2026-13676
- https://bugzilla.redhat.com/show_bug.cgi?id=2494197
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-13676.json
References
- https://github.com/fastify/fast-uri/security/advisories/GHSA-4c8g-83qw-93j6
- https://cna.openjsf.org/security-advisories.html
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.