All vulnerabilities

npm

CVE-2026-16221

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

Severity
High 7.5
Published
21 Jul 2026
Last changed
10 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
2.4.3, 3.1.4, 4.1.1
Exploit chance
0.4% in the next 30 daysHigher than 38% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-436
Attack
Over the network · No login needed · No user action needed
Attacker can
Change data
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Also known as
GHSA-v2hh-gcrm-f6hx
Sources
OSV.dev and GitHub

Description

fast-uri v4.1.0 and earlier do not treat a literal backslash (U+005C) as an authority delimiter. Node's native WHATWG URL (used by fetch(), undici, and Node's http/https clients) normalizes \ to / for special schemes (http, https, ws, wss, ftp, file), so the two parsers extract different hosts from the same input string.

For example, http://evil.com\@allowed.com is treated by fast-uri as host allowed.com with userinfo evil.com\, while Node's WHATWG URL parser and fetch() see host evil.com with path /@allowed.com.

Applications that use fast-uri to enforce host-based policy (allowlists, denylists, loopback/SSRF filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL or fetch() consumers see a policy/use desync and can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts.

From the GitHub Advisory Database, CC BY 4.0.

Workarounds

None. Upgrade to the patched version.

Workarounds as given by the GitHub Advisory Database, CC BY 4.0.

Affected software

SoftwareAffected versions
fast-urinpm · osv:npm:fast-uri
  • From 2.3.1 before 2.4.3
  • From 3.0.0 before 3.1.4
  • From 4.0.0 before 4.1.1

About fast-uri

Weekly downloads (npm)
227,816,128npm, 17 Nov 2026

References