CVE-2026-75975: fast-uri vulnerable to server-side request forgery via malformed IPv6 normalization
High CVSS 7.5
- OSV id
- GHSA-f65p-4m7j-42xc
- Also known as
- CVE-2026-75975
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| fast-uri npm |
>= 2.3.1, < 2.4.5 | 2.4.5 |
| fast-uri npm |
>= 3.0.0, < 3.1.6 | 3.1.6 |
| fast-uri npm |
>= 4.0.0, < 4.1.3 | 4.1.3 |
Versions we track that it affects: fast-uri 3.1.5; fast-uri 3.1.5; fast-uri 3.1.5
How to fix it
fast-uri (npm)
Upgrade fast-uri to 2.4.5 or later.
npm install fast-uri@2.4.5
# if it is an indirect dependency: npm update fast-uri (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
fast-uri (npm)
Upgrade fast-uri to 3.1.6 or later.
npm install fast-uri@3.1.6
# if it is an indirect dependency: npm update fast-uri (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
fast-uri (npm)
Upgrade fast-uri to 4.1.3 or later.
npm install fast-uri@4.1.3
# if it is an indirect dependency: npm update fast-uri (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
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.
References
- GHSA-f65p-4m7j-42xc on OSV.dev
- Web: https://github.com/fastify/fast-uri/security/advisories/GHSA-f65p-4m7j-42xc
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-75975
- Web: https://github.com/fastify/fast-uri/commit/3728465caacef4b16bc84b7d14760f1c8fe41595
- Web: https://github.com/fastify/fast-uri/commit/607bfbe953f28a14c2e06ae64aff38c81ca2937f
- Web: https://github.com/fastify/fast-uri/commit/9161eded1ff55fad9d9714c6ad6c0f0283547799
- Web: https://cna.openjsf.org/security-advisories.html
- Package: https://github.com/fastify/fast-uri
- Web: https://github.com/fastify/fast-uri/releases/tag/v2.4.5
- Web: https://github.com/fastify/fast-uri/releases/tag/v3.1.6
- Web: https://github.com/fastify/fast-uri/releases/tag/v4.1.3
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.