fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization

Summary

fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions from 2.4.2 through 2.4.7, from 3.1.3 through 3.1.8, and from 4.0.1 through 4.2.2, for HTTP-family schemes the canonicalizeHost() function passes the parsed host to the WHATWG URL parser and adopts its hostname without checking that the parser consumed the entire input as a host, so the authority can be silently rewritten: data before an at-sign is dropped and tab, carriage-return, and line-feed characters are stripped, with no error reported. An application that enforces host-based policy such as denylists, loopback filtering, redirect validation, or outbound proxy routing on one representation can then see the canonical host diverge from what it checked, allowing traffic to be steered to an unintended destination. 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 an authority that contains more than one at-sign or any tab, carriage-return, or line-feed before calling fast-uri, or treat any non-empty parse error as fatal and compare hosts only from the same parse result.

Timeline

1. Oct 20, 2026, 7:00 AM UTCCVE published
2. Oct 20, 2026, 4:06 PM UTCCISA SSVC assessment

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

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

Affected versions

• fast-uri fast-uri

  From 2.4.2 · fixed in 2.4.8; From 3.1.3 · fixed in 3.1.9; From 4.0.1 · fixed in 4.2.3

• fast-urinpm

  From 2.4.2 · fixed in 2.4.8

• fast-urinpm

  From 3.1.3 · fixed in 3.1.9

• fast-urinpm

  From 4.0.1 · fixed in 4.2.3

References 2