fast-uri vulnerable to URI scheme spoofing via percent-encoded scheme decoding

Summary

fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and from 4.0.0 through 4.2.2, fast-uri percent-decodes the scheme component with the legacy global unescape() function before validating it, so an input whose decoded scheme is a dangerous token is emitted as a live scheme even though RFC 3986 does not allow percent-encoding in a scheme and no other parser accepts it. An application that screens dangerous schemes on the raw input and then stores or renders the normalized or resolved result can turn an inert string into an executable javascript, data, or vbscript URL, producing a stored or reflected cross-site scripting vector, and the equal() comparison treats an encoded and a plain scheme as the same, which can bypass equality-based allowlists. The issue is fixed in fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these versions or later. As a workaround, reject input whose scheme part contains a percent sign, or check the parsed scheme against an allowlist after normalization and use that same parsed result rather than the raw string.

Timeline

1. Oct 20, 2026, 7:03 AM UTCCVE published
2. Oct 20, 2026, 7:14 PM UTCCISA SSVC assessment

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

3. Oct 20, 2026, 7:14 PM UTCRecord last updated
4. Oct 22, 2026, 9:34 PM UTCFirst seen by cve.now

Affected versions

• fast-uri fast-uri

  fixed in 2.4.8; From 3.0.0 · fixed in 3.1.9; From 4.0.0 · fixed in 4.2.3

• fast-urinpm

  fixed in 2.4.8

• fast-urinpm

  From 3.0.0 · fixed in 3.1.9

• fast-urinpm

  From 4.0.0 · fixed in 4.2.3

References 2