CVE-2026-110725: fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references
Low CVSS 3.7
- OSV id
- GHSA-333x-w4r6-6crp
- Also known as
- CVE-2026-110725
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| fast-uri npm |
< 2.4.8 | 2.4.8 |
| fast-uri npm |
>= 3.0.0, < 3.1.9 | 3.1.9 |
| fast-uri npm |
>= 4.0.0, < 4.2.3 | 4.2.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.8 or later.
npm install fast-uri@2.4.8
# 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.9 or later.
npm install fast-uri@3.1.9
# 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.2.3 or later.
npm install fast-uri@4.2.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's serialize(), normalize(), and resolve(), when called with the non-default option reference: 'suffix' on a reference that has no authority, emit a relative reference whose first path segment contains a bare colon without escaping it. RFC 3986 section 3.3 requires the first segment of a path-noscheme reference not to contain a colon, precisely because a bare colon makes the string reparse as an absolute URI with a scheme. fast-uri's default serialization escapes that colon, but the suffix path does not.
For example, normalize('javascript:alert(1)', { reference: 'suffix' }) returns javascript:alert(1), which reparses as a live javascript: scheme; data: and vbscript: behave the same.
Applications that serialize or normalize a relative reference with reference: 'suffix' and then treat the result as a URI can turn inert input into a live javascript:, data:, or vbscript: URL (a cross-site scripting vector), and equal() can conflate a scheme-bearing reference with a relative one. Exposure is limited to applications that use the non-default reference: 'suffix' option.
Patches
Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.
Workarounds
Do not use the reference: 'suffix' option on untrusted input. If suffix output is required, percent-encode a colon in the first path segment of the result before treating it as a URI.
References
- GHSA-333x-w4r6-6crp on OSV.dev
- Web: https://github.com/fastify/fast-uri/security/advisories/GHSA-333x-w4r6-6crp
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-110725
- Web: https://github.com/fastify/fast-uri/commit/39e6493c1356f30a0084171627eb266786e1620e
- Web: https://github.com/fastify/fast-uri/commit/a9b8d67353630aab053cd727cf629023dd018d2b
- 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.8
- Web: https://github.com/fastify/fast-uri/releases/tag/v3.1.9
- Web: https://github.com/fastify/fast-uri/releases/tag/v4.2.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.