CVE-2026-13676

fast-uri vulnerable to host confusion via failed IDN canonicalization

HIGH
7.5
CVSS Score
Published: June 29, 2026 at 01:22 PM UTC
Updated: September 11, 2026 at 01:50 PM UTC
18 products affected across 3 vendorsFast UriEnterprise LinuxOpenShift Container Platform

Using fast-uri by fast-uri?

Get instant alerts when new vulnerabilities affect fast-uri - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.3.1 ≤ v < 3.1.34.0.0 ≤ v < 4.0.1
Affected range stops below 3.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.1, so it looks safe — our inference, not a vendor statement
2.3.1 ≤ v < 3.1.34.0.0 ≤ v < 4.0.12.3.14.0.0
Vendor states this is fixed in 3.1.3 (unaffected)
Vendor states this is fixed in 4.0.1 (unaffected)
Vendor states this is fixed in 1784622951 (unaffected)
Vendor states this is fixed in 1785413994 (unaffected)
Vendor states this is fixed in 1785773509 (unaffected)
Vendor states this is fixed in 2 (unaffected)
Vendor states this is fixed in 0:1.1.2-1.el10_2 (unaffected)

References (45)

Vendor Advisory
Source: cverecord
https://cna.openjsf.org/security-advisories.html
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-13676
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2494197
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-13676.json
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:37186
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:37585
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:37628

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHopenjs
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-436CWE-551

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card