CVE-2026-110180: fast-uri vulnerable to host confusion via unchecked WHATWG host canonicalization
Impact fast-uri versions = 2.4.2, = 3.1.3, = 4.0.1, <= 4.2.2 can silently rewrite the host of an HTTP-family URL (http, https, ws, wss, or any scheme with domainHost: true). For those schemes canonicalizeHost() passes the parsed host to the WHATWG URL parser and adopts its .hostname without checking that the parser read the whole input as a host.
Published Oct 23, 2026
Affected packages
fast-uri
- Ecosystem
- npm
- Affected
- >= 2.4.2, < 2.4.8
- Fixed in
- 2.4.8
- Check
npm ls fast-uri
fast-uri
- Ecosystem
- npm
- Affected
- >= 3.1.3, < 3.1.9
- Fixed in
- 3.1.9
- Check
npm ls fast-uri
fast-uri
- Ecosystem
- npm
- Affected
- >= 4.0.1, < 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 versions >= 2.4.2, <= 2.4.7, >= 3.1.3, <= 3.1.8, and >= 4.0.1, <= 4.2.2 can silently rewrite the host of an HTTP-family URL (http, https, ws, wss, or any scheme with domainHost: true). For those schemes canonicalizeHost() passes the parsed host to the WHATWG URL parser and adopts its .hostname without checking that the parser read the whole input as a host. RFC 3986 permits @ inside the host group and the WHATWG parser strips TAB, LF, and CR, so the authority fast-uri reports is rewritten by that second parser with no error set: data before an @ is dropped and whitespace is removed.
For example, fast-uri parses http://a@[email protected]/ to host evil.example (dropping the b segment), and a host containing a raw TAB, CR, or LF has those characters stripped. equal() then treats a whitespace-smuggled host as the same as the clean one, and resolve() rewrites the authority the same way.
Applications that use fast-uri to enforce host-based policy (denylists, loopback filtering, redirect validation, outbound proxy routing) on one representation, such as the raw input, see a policy/use desync: the canonical host fast-uri returns differs from what was checked, and traffic can be steered to an unintended destination.
Patches
Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.
Workarounds
Reject URIs whose authority contains more than one @, or contains TAB, CR, or LF, before calling fast-uri. Alternatively, treat any non-empty parse(x).error as fatal, and compare hosts only from the same parse() result.
Credited to UlisesGascon, mcollina.
References
- https://github.com/fastify/fast-uri/security/advisories/GHSA-wjr9-j795-jxcr
- https://nvd.nist.gov/vuln/detail/CVE-2026-110180
- https://github.com/fastify/fast-uri/commit/58c183d0b168ad87f98773266444ce1f6375803a
- https://github.com/fastify/fast-uri/commit/ddfc6a51122dfce0365655f04479fc3adb7f6b3c
- https://github.com/fastify/fast-uri/commit/f6d46dfeab025d0c440485f4ae29fa4f14707646
- 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-wjr9-j795-jxcr
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-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, 2026CVE-2026-84292
fast-uri vulnerable to authority injection via an unvalidated port in serialize
high7.5Sep 28, 2026
