fast-uri vulnerable to host confusion via percent-encoded scheme normalization

Summary

fast-uri is a URI parser for Node.js. During parsing it runs a legacy decoding pass over the scheme component and never re-escapes the result, and serialization writes the scheme back out verbatim, unlike the host component which is re-escaped. As a result an input whose scheme carries percent-encoded slashes parses as a scheme with no authority, so the parsed host and error are both undefined, yet resolving or normalizing that same input emits a network-path reference whose authority is attacker-chosen and re-parses to that host. An application that allowlists on the parsed host, or treats a reference with no authority as safe to resolve against its base, gets the opposite of what it checked, giving an off-site redirect, server-side request forgery, or address-policy bypass. The legacy decoder also expands non-standard escape forms, widening the issue past upstream filters, and control characters in the scheme can reach the output as raw carriage return and line feed. The affected versions are 2.3.1 up to but not including 2.4.5, 3.0.0 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which reject a scheme that is not valid after decoding. Users should upgrade to a patched version.

Timeline

1. Aug 24, 2026, 10:07 AM UTCCVE published
2. Aug 24, 2026, 2:29 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Aug 24, 2026, 2:29 PM UTCRecord last updated

Affected versions

• fast-uri fast-uri

  From 2.3.1 · fixed in 2.4.5; From 3.0.0 · fixed in 3.1.6; From 4.0.0 · fixed in 4.1.3

• fast-urinpm

  From 2.3.1 · fixed in 2.4.5

• fast-urinpm

  From 3.0.0 · fixed in 3.1.6

• fast-urinpm

  From 4.0.0 · fixed in 4.1.3

References 2