CVE-2026-75931: fast-uri vulnerable to host confusion via skipped IDN canonicalization on scheme-relative references
High CVSS 7.5
- OSV id
- GHSA-5jgf-p345-68v8
- Also known as
- CVE-2026-75931
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| fast-uri npm |
>= 2.4.2, < 2.4.5 | 2.4.5 |
| fast-uri npm |
>= 3.1.3, < 3.1.6 | 3.1.6 |
| fast-uri npm |
>= 4.0.1, < 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 canonicalizes a host to its ASCII form only when the input carries an explicit scheme. When resolve() resolves a scheme-relative reference (//host/) against a scheme-bearing base, it still emits the host verbatim even though the effective scheme is known, so re-parsing the resolved URI yields a different host than the one resolve() returned. An application that resolves an untrusted reference with fast-uri and then checks or routes on the resulting host can make a policy decision on one host and reach another. This is an incomplete-fix variant of CVE-2026-13676, whose IDN canonicalization was applied only to the scheme-bearing form.
Patches
Upgrade to fast-uri 2.4.5, 3.1.6, or 4.1.3. resolve() now canonicalizes the host once the effective scheme is known, and fails closed if a raw non-ASCII host cannot be converted.
Workarounds
Resolve scheme-relative references against a base that carries a scheme before performing any host-policy or origin check.
References
- GHSA-5jgf-p345-68v8 on OSV.dev
- Web: https://github.com/fastify/fast-uri/security/advisories/GHSA-5jgf-p345-68v8
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-75931
- Web: https://github.com/fastify/fast-uri/commit/0256bc8d1f28b5d0ac657faf67e2411a189dfcb5
- Web: https://github.com/fastify/fast-uri/commit/444ecdad447db2cc23c4d422acc6f0daa6fa8eef
- Web: https://github.com/fastify/fast-uri/commit/4e4ebd8b245f6ca16e448203559eea3e545453a3
- 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.