fast-uri vulnerable to server-side request forgery via repeated hostname percent-decoding

Summary

fast-uri is a URI parser for Node.js. It decodes percent escapes in a hostname during parsing and then decodes the parsed hostname a second time during authority recomposition, so a single call to normalize or resolve can turn nested percent-encoded input into a different network destination such as a loopback hostname or address. For example, a doubly encoded host that spells out a loopback name decodes to that live host in one operation, which contradicts RFC 3986 section 2.4 that an implementation must not decode the same string more than once. An application that normalizes or resolves an untrusted HTTP-family URI before outbound routing, redirect validation, or a host-policy check can receive a destination different from the one the original encoded host represented, giving a server-side request forgery and host-policy bypass primitive. This is an incomplete-fix variant of CVE-2026-6322. The affected versions are 2.4.1 up to but not including 2.4.5, 3.1.2 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 normalize percent escapes once and preserve encoded percent signs. Users should upgrade to a patched version.

Timeline

1. Aug 24, 2026, 9:40 AM UTCCVE published
2. Aug 24, 2026, 4:16 PM UTCCISA SSVC assessment

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

3. Aug 24, 2026, 4:19 PM UTCRecord last updated

Affected versions

• fast-uri fast-uri

  From 2.4.1 · fixed in 2.4.5; From 3.1.2 · fixed in 3.1.6; From 4.0.0 · fixed in 4.1.3

• fast-urinpm

  From 2.4.1 · fixed in 2.4.5

• fast-urinpm

  From 3.1.2 · fixed in 3.1.6

• fast-urinpm

  From 4.0.0 · fixed in 4.1.3

References 2