CVE-2026-16221

fast-uri vulnerable to host confusion via literal backslash authority delimiter

HIGH
7.5
CVSS Score
Published: July 19, 2026 at 02:08 PM UTC
Updated: August 5, 2026 at 08:01 PM UTC
2 products affected across 2 vendorsFast UriFast Uri

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.4%
SSVC
No known exploit

Description

Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x line up to 3.1.3 and the 2.x line up to 2.4.2) do not treat a literal backslash character (U+005C) as an authority delimiter. Node's native WHATWG URL parser, used by fetch, undici, and Node's http and https clients, normalizes the backslash to a forward slash for special schemes such as http, https, ws, wss, ftp, and file. As a result, the two parsers extract different hosts from the same input string. Applications that use fast-uri to enforce host-based policy such as allowlists, denylists, loopback or SSRF filtering, redirect validation, or outbound proxy routing before passing the same URL into Node's URL or fetch consumers can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts. Patches: upgrade to fast-uri 4.1.1, 3.1.4, or 2.4.3. Workarounds: none.

Affected

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

2.3.1 ≤ v < 2.4.33.0.0 ≤ v < 3.1.44.0.0 ≤ v < 4.1.1
Affected range stops below 2.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.1, so it looks safe — our inference, not a vendor statement
2.3.1 ≤ v < 2.4.33.0.0 ≤ v < 3.1.44.0.0 ≤ v < 4.1.12.3.13.0.04.0.0
Vendor states this is fixed in 2.4.3 (unaffected)
Vendor states this is fixed in 3.1.4 (unaffected)
Vendor states this is fixed in 4.1.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

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

StatusANALYZED
CWE
CWE-436

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