CVE-2026-110725: fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references
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.
Published Oct 23, 2026
Affected packages
fast-uri
- Ecosystem
- npm
- Affected
- < 2.4.8
- Fixed in
- 2.4.8
- Check
npm ls fast-uri
fast-uri
- Ecosystem
- npm
- Affected
- >= 3.0.0, < 3.1.9
- Fixed in
- 3.1.9
- Check
npm ls fast-uri
fast-uri
- Ecosystem
- npm
- Affected
- >= 4.0.0, < 4.2.3
- Fixed in
- 4.2.3
- Check
npm ls fast-uri
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to UlisesGascon, mcollina.
References
- https://github.com/fastify/fast-uri/security/advisories/GHSA-333x-w4r6-6crp
- https://nvd.nist.gov/vuln/detail/CVE-2026-110725
- https://github.com/fastify/fast-uri/commit/39e6493c1356f30a0084171627eb266786e1620e
- https://github.com/fastify/fast-uri/commit/a9b8d67353630aab053cd727cf629023dd018d2b
- https://cna.openjsf.org/security-advisories.html
- https://github.com/fastify/fast-uri/releases/tag/v2.4.8
- https://github.com/fastify/fast-uri/releases/tag/v3.1.9
- https://github.com/fastify/fast-uri/releases/tag/v4.2.3
- https://github.com/advisories/GHSA-333x-w4r6-6crp
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-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, 2026CVE-2026-84292
fast-uri vulnerable to authority injection via an unvalidated port in serialize
high7.5Sep 28, 2026
