Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-110180 Overview
CVE-2026-110180 is an input validation flaw [CWE-20] in fast-uri, a dependency-free RFC 3986 URI parser and serializer for Node.js. The canonicalizeHost() function accepts the WHATWG URL parser output without verifying the parser consumed the entire input as a host. Attackers can craft authority strings where data before an at-sign is silently dropped, and tab, carriage-return, and line-feed characters are stripped without error. Applications that apply host-based policy on one representation and route traffic on another see divergent hostnames, allowing policy bypass.
Critical Impact
Host-based denylists, loopback filters, redirect validators, and outbound proxy routing can be bypassed, steering traffic to attacker-controlled destinations.
Affected Products
- fast-uri versions 2.4.2 through 2.4.7
- fast-uri versions 3.1.3 through 3.1.8
- fast-uri versions 4.0.1 through 4.2.2
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-110180 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-110180
Vulnerability Analysis
The flaw lives in canonicalizeHost() within fast-uri. For HTTP-family schemes, the function delegates host parsing to the WHATWG URL parser and adopts the returned hostname. It does not confirm the parser consumed the entire input as a host component. As a result, two silent transformations occur without any error being reported to the caller.
First, any characters preceding an at-sign (@) in the authority are discarded, because the WHATWG parser treats them as userinfo. Second, tab (\t), carriage-return (\r), and line-feed (\n) characters embedded in the authority are stripped. The caller receives a canonical host that does not match the raw input it inspected.
Security controls that depend on comparing a validated host against the host actually used for connection logic are directly affected. An application might validate attacker.com@internal.service by rejecting attacker.com, then route the request to internal.service after canonicalization. Equivalent divergence applies to loopback filtering, SSRF defenses, redirect validation, and outbound proxy rules.
Root Cause
The root cause is improper input validation [CWE-20]. The parser output is trusted without checking that the full authority was consumed as a host, so hidden rewrites of the authority pass through undetected.
Attack Vector
An attacker supplies a crafted URI to any application that passes user-controlled input through fast-uri and applies host-based policy decisions. The attack requires no authentication and is network-reachable, but exploitation depends on the application's specific policy enforcement pattern.
See the GitHub Security Advisory GHSA-wjr9-j795-jxcr for authoritative technical details.
Detection Methods for CVE-2026-110180
Indicators of Compromise
- Inbound requests containing URIs with an at-sign (@) in the authority component, especially when the pre-@ segment is a public or allowlisted domain.
- Authority strings containing embedded \t, \r, or \n control characters.
- Outbound connections from Node.js services to hosts that do not match the host logged during request validation.
Detection Strategies
- Audit application logs for divergence between the host string checked by policy code and the host used by downstream HTTP clients.
- Inspect dependency manifests (package.json, package-lock.json, yarn.lock) for vulnerable fast-uri version ranges.
- Add instrumentation around canonicalizeHost() call sites to log inputs containing @, \t, \r, or \n in the authority.
Monitoring Recommendations
- Monitor egress traffic from Node.js workloads for connections to internal or loopback addresses correlated with external user input.
- Alert on web application firewall events that observe at-signs or control characters in URL authority components.
- Track SBOM changes to confirm fast-uri upgrades propagate to all deployed services.
How to Mitigate CVE-2026-110180
Immediate Actions Required
- Upgrade fast-uri to version 2.4.8, 3.1.9, 4.2.3, or later across all services and transitive dependencies.
- Inventory applications that use fast-uri for host-based policy enforcement and prioritize them for patching.
- Re-review redirect validators, SSRF filters, and outbound proxy rules that rely on fast-uri output.
Patch Information
The maintainers resolved the issue in fast-uri2.4.8, 3.1.9, and 4.2.3. Upgrade to one of these versions or later. Refer to the OpenJSF Security Advisories for coordinated disclosure details.
Workarounds
- Reject any authority containing more than one at-sign before invoking fast-uri.
- Reject any authority containing tab, carriage-return, or line-feed characters prior to parsing.
- Treat any non-empty parse error as fatal and compare hosts only from the same parse result, never across representations.
# Upgrade fast-uri to a fixed release
npm install fast-uri@^4.2.3
# Or for the 3.x line
npm install fast-uri@^3.1.9
# Or for the 2.x line
npm install fast-uri@^2.4.8
# Verify no vulnerable versions remain in the tree
npm ls fast-uri
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

