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-110095 Overview
CVE-2026-110095 is a path normalization flaw in fast-uri, a dependency-free RFC 3986 URI parser and serializer for Node.js. The normalize() and serialize() functions incorrectly apply RFC 3986 dot-segment removal to relative-path references. That algorithm is defined only for the merged target path during resolution. As a result, a leading parent-directory segment can be dropped, converting a document-relative reference into a root-relative one. Applications that normalize attacker-supplied references and use them for resolution, caching, deduplication, or authorization keys may route requests to unintended resources.
Critical Impact
An attacker-controlled relative URI can escape its intended directory, enabling cache or authorization key confusion in applications that normalize before resolving.
Affected Products
- fast-uri versions prior to 2.4.8
- fast-uri versions 3.0.0 through 3.1.8
- fast-uri versions 4.0.0 through 4.2.2
Discovery Timeline
- 2026-10-20 - CVE-2026-110095 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-110095
Vulnerability Analysis
The flaw is classified as [CWE-41] Improper Resolution of Path Equivalence. RFC 3986 Section 5.2.4 specifies the remove_dot_segments algorithm as a step applied to the merged target path during reference resolution. fast-uri applies this routine directly inside normalize() and serialize() against the path of any relative-path reference. The algorithm removes .. segments that it treats as redundant at the start of a path. On a relative reference, those leading segments carry semantic meaning and change which parent directory the reference points to.
Stripping the leading .. turns a reference like ../admin/config into admin/config. When the host application later resolves the normalized value against a base URI, the result points to a different directory than the user intended. The impact escalates when the normalized string is used as a cache key, deduplication key, or authorization lookup. Two distinct resources collapse to the same key and inherit each other's trust decisions.
Root Cause
The normalization routine does not distinguish between an absolute path and a relative-path reference before invoking dot-segment removal. RFC 3986 reserves that step for post-merge paths only. Applying it earlier violates the reference semantics defined in Section 4.2.
Attack Vector
Exploitation requires an application that accepts a relative URI from an untrusted source, passes it through fast-urinormalize() or serialize(), and then either resolves it against a base or treats the normalized string as an identity key. The attacker crafts a reference whose leading parent-directory segments are stripped by normalization. Attack complexity is high because the target application must perform specific downstream operations on the normalized output for impact to materialize. See the GitHub Security Advisory GHSA-xhq7-xmqj-769h for the technical write-up.
Detection Methods for CVE-2026-110095
Indicators of Compromise
- Cache or authorization logs showing requests resolving to resources outside the expected directory scope for a given user session.
- Duplicate cache entries collapsing to the same normalized key despite originating from distinct relative references.
- Unexpected 2xx responses for paths that should have been rejected by directory-scoped access control.
Detection Strategies
- Audit application dependency manifests (package.json, package-lock.json, yarn.lock) for vulnerable fast-uri versions.
- Instrument calls to fast-uri.normalize() and fast-uri.serialize() to log input and output, and alert when leading .. segments disappear.
- Run software composition analysis across Node.js services and container images to flag transitive dependencies on affected versions.
Monitoring Recommendations
- Monitor web application logs for authorization decisions that permit access to resources outside a user's expected namespace.
- Track cache hit anomalies where unrelated clients receive identical cached responses.
- Alert on dependency drift that reintroduces fast-uri versions below the fixed releases.
How to Mitigate CVE-2026-110095
Immediate Actions Required
- Upgrade fast-uri to version 2.4.8, 3.1.9, 4.2.3, or later across all Node.js services.
- Enumerate transitive dependencies and force resolution to a patched version where parent packages pin an older release.
- Review code paths that normalize URIs before resolution and refactor to normalize only the resolved absolute URI.
Patch Information
The maintainers released fixes in fast-uri 2.4.8, 3.1.9, and 4.2.3. See the OpenJS Foundation Security Advisories and the GitHub Security Advisory GHSA-xhq7-xmqj-769h for release details.
Workarounds
- Resolve the relative reference against its absolute base URI first, then normalize the resulting absolute URI.
- Avoid using normalized relative references as cache, deduplication, or authorization keys until the dependency is patched.
- Add input validation that rejects relative references containing leading .. segments when the application context does not expect directory traversal.
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

