Skip to content
Connect AISign inSign up free
CVE-2026-1100953.7LowCWE-41

CVE-2026-110095: fast-uri vulnerable to improper path equivalence in relative reference normalization

fast-uri

Fixed in 2.4.8 · Affected: fast-uri before 2.4.8 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.3%probability of exploitation in the next 30 days
21st percentile
050100

Higher than 21% of scored CVEs

3.7LowCVSS 3.1
Low

DescriptionCVE.org

fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and from 4.0.0 through 4.2.2, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. The issue is fixed in fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these versions or later. As a workaround, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • fast-uri · fast-uribefore 2.4.8; from 3.0.0 before 3.1.9; from 4.0.0 before 4.2.3

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
fast-uri
Published
October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-110095 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References