CVE-2026-75975: fast-uri vulnerable to server-side request forgery via malformed IPv6 normalization
Impact fast-uri does not validate the complete RFC 3986 grammar for bracketed IPv6 literals, so a malformed literal with invalid trailing text is silently truncated to a different valid IPv6 address with no error reported. For example, normalize('http://[::not-valid]/private') returns http://[::]/private, and [fc00::not-hex] and [fe80::not-hex] collapse to [fc00::] and [fe80::].
Published Sep 2, 2026
Affected packages
fast-uri
- Ecosystem
- npm
- Affected
- >= 2.3.1, < 2.4.5
- Fixed in
- 2.4.5
- Check
npm ls fast-uri
fast-uri
- Ecosystem
- npm
- Affected
- >= 3.0.0, < 3.1.6
- Fixed in
- 3.1.6
- Check
npm ls fast-uri
fast-uri
- Ecosystem
- npm
- Affected
- >= 4.0.0, < 4.1.3
- Fixed in
- 4.1.3
- Check
npm ls fast-uri
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
fast-uri does not validate the complete RFC 3986 grammar for bracketed IPv6 literals, so a malformed literal with invalid trailing text is silently truncated to a different valid IPv6 address with no error reported. For example, normalize('http://[::not-valid]/private') returns http://[::]/private, and [fc00::not-hex] and [fe80::not-hex] collapse to [fc00::] and [fe80::]. An application that normalizes an untrusted URL before an outbound request, redirect, or host-policy check can be routed to a local or private address such as loopback (::1), unique-local, or link-local. Because parse().error is unset for these inputs, checking it does not protect the consumer.
Patches
Upgrade to fast-uri 2.4.5, 3.1.6, or 4.1.3. Malformed IPv6 literals are now rejected with a host error instead of being normalized to a valid address.
Workarounds
Reject untrusted URLs whose host is a bracketed IPv6 literal before passing them to fast-uri, or route outbound requests against an explicit allowlist of addresses rather than trusting the normalized host.
Credited to mcollina, UlisesGascon.
References
- https://github.com/fastify/fast-uri/security/advisories/GHSA-f65p-4m7j-42xc
- https://nvd.nist.gov/vuln/detail/CVE-2026-75975
- https://github.com/fastify/fast-uri/commit/3728465caacef4b16bc84b7d14760f1c8fe41595
- https://github.com/fastify/fast-uri/commit/607bfbe953f28a14c2e06ae64aff38c81ca2937f
- https://github.com/fastify/fast-uri/commit/9161eded1ff55fad9d9714c6ad6c0f0283547799
- https://cna.openjsf.org/security-advisories.html
- https://github.com/fastify/fast-uri/releases/tag/v2.4.5
- https://github.com/fastify/fast-uri/releases/tag/v3.1.6
- https://github.com/fastify/fast-uri/releases/tag/v4.1.3
- https://github.com/advisories/GHSA-f65p-4m7j-42xc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-110095
fast-uri vulnerable to improper path equivalence in relative reference normalization
low3.7Oct 23, 2026CVE-2026-110180
fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization
medium4.8Oct 23, 2026CVE-2026-110306
fast-uri vulnerable to URI scheme spoofing via percent-encoded scheme decoding
medium6.1Oct 23, 2026CVE-2026-110725
fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references
low3.7Oct 23, 2026CVE-2026-86472
fast-uri vulnerable to inconsistent host case normalization via percent-encoded octets
medium4.8Sep 29, 2026CVE-2026-86818
fast-uri vulnerable to mailto header injection via percent-encoded field-name desynchronization
medium4.8Sep 29, 2026
