CVE-2026-16221

published 19 Jul 2026 · updated 20 Jul 2026

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

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.4.3, 3.1.4 and 4.1.1.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
fast-uri>=2.3.1 <2.4.3, >=3.0.0 <3.1.4, >=4.0.0 <4.1.12.4.3, 3.1.4, 4.1.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-16221 severity on Zeptric[![CVE-2026-16221](https://zeptric.io/badge/cve/CVE-2026-16221.svg)](https://zeptric.io/cve/CVE-2026-16221)