All vulnerabilities

npm

CVE-2026-13676

fast-uri vulnerable to host confusion via failed IDN canonicalization

Severity
High 7.5
Published
21 Jul 2026
Last changed
11 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
2.4.2, 3.1.3, 4.0.1
Exploit chance
0.7% in the next 30 daysHigher than 53% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-436CWE-551
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-4c8g-83qw-93j6
Sources
OSV.dev and GitHub

Description

fast-uri versions >= 2.3.1, <= 4.0.0 fail to canonicalize Unicode/IDN hostnames for HTTP-family URLs. The IDN conversion path calls URL.domainToASCII(...) on the global WHATWG URL constructor, where that helper does not exist. The resulting TypeError is silently routed into parsed.error, but parse(), normalize(), and equal() all return with the host left in its original Unicode form.

For example, http://127。0。0。1/ is treated by fast-uri as host 127。0。0。1, while Node's WHATWG URL parser and fetch() canonicalize the same input to 127.0.0.1.

Applications that use fast-uri to enforce host-based policy (denylists, loopback 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.

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.2
  • From 3.0.0 before 3.1.3
  • From 4.0.0 before 4.0.1

About fast-uri

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

References