Packages / fast-uri / Security

ModerateVulnerabilityGHSA-hrr3-gc8f-f4qjCVE-2026-86472Published 29 Sep 2026

fast-uri vulnerable to inconsistent host case normalization via percent-encoded octets

Your version

Affected releases · fast-uri

  • 4.x4.0.0 – 4.1.4Fixed in 4.1.5
  • 3.x3.0.0 – 3.1.7Fixed in 3.1.8
  • 2.x2.0.0 – 2.4.6Fixed in 2.4.7
  • 1.x and older0.0.1 – 1.0.1No fix, no longer updated

On 4.x, the newest line:

npm install fast-uri@4.1.5
Every release on a timeline
4.x
  1. Affected

    4.0.0 – 4.1.4

    7 releases

  2. Fixed

    4.1.5 – 4.2.3

    5 releases, latest

3.x
  1. Affected

    3.0.0 – 3.1.7

    15 releases

  2. Fixed

    3.1.8 – 3.1.9

    2 releases

2.x
  1. Affected

    2.0.0 – 2.4.6

    12 releases

  2. Fixed

    2.4.7 – 2.4.8

    2 releases

1.x
  1. Affected

    1.0.0 – 1.0.1

    2 releases

0.x
  1. Affected

    0.0.1 – 0.0.2

    2 releases

47 stable releases of fast-uri, oldest to newest, one row per major.

What happens

Impact

fast-uri folds the host to lowercase before it percent-decodes the host, so a percent-encoded uppercase unreserved octet such as %41 decodes to a literal A that is never folded. For a scheme-relative reference (//host) there is no scheme, so the host canonicalization that repairs this on a scheme-bearing URL does not run. As a result parse, normalize, and equal disagree on the same host: parse("//%41.com").host returns "A.com" while parse("//a.com").host and parse("//A.com").host return "a.com", and equal("//%41.com", "//a.com") is false even though equal("//A.com", "//a.com") is true. An application that makes a case-sensitive host decision on fast-uri output for a scheme-relative reference, for example a host allowlist or denylist that compares parse(url).host or uses fast-uri.equal, can be steered past the check with a percent-encoded uppercase octet. Because a hostname is case-insensitive in DNS and HTTP routing, the evading spelling reaches the same host the check meant to gate, so the effect is check evasion rather than reaching a different registrable host.

Patches

Upgrade to fast-uri 4.1.5, 3.1.8, or 2.4.7.

Workarounds

Compare hosts case-insensitively (lowercase the parsed host before any allowlist or denylist decision), or avoid making case-sensitive host decisions on scheme-relative input until upgrading.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.