Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

fast-uri vulnerable to improper path equivalence in relative reference normalization

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-110095

Published

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.

Source published
20 Oct 2026 06:56:56 UTC
Source modified
20 Oct 2026 16:07:47 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

euvd · EUVD-2026-104812

Published

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 20, 2026, 6:56:56 AM

dateUpdated: Oct 20, 2026, 4:07:47 PM

6 related source bulletins · separate from aliases

openSUSE-SU-2026:12531-1: mcp-server-everything-2.4.0-1.1 on GA media

CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725

RHSA-2026:91292: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

CVE-2026-79656 · CVE-2026-100352 · CVE-2026-100353 · CVE-2026-100354 · CVE-2026-103506 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-111181

RHSA-2026:91181: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

CVE-2026-16491 · CVE-2026-79656 · CVE-2026-103506 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-111181

openSUSE-SU-2026:12261-1: git-bug-0.11.0-3.1 on GA media

CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-110816 · CVE-2026-111756 · CVE-2026-112085 · CVE-2026-112366 · CVE-2026-78659 · CVE-2026-78660 · CVE-2026-78663 · CVE-2026-78669 · CVE-2026-97032

RHSA-2026:90990: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

CVE-2026-16491 · CVE-2026-79656 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-111181

RHSA-2026:90388: Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

CVE-2026-16491 · CVE-2026-65627 · CVE-2026-100352 · CVE-2026-100353 · CVE-2026-100354 · CVE-2026-110095 · CVE-2026-110180 · CVE-2026-110306 · CVE-2026-110725 · CVE-2026-110816 · CVE-2026-111181

Source published
Oct 20, 2026, 6:56:56 AM (timezone not stated)
Source modified
Oct 20, 2026, 4:07:47 PM (timezone not stated)
Saved here
17 Nov 2026 13:35:16 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

nvd · CVE-2026-110095

Published

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Awaiting Analysis

Weakness classifications: CWE-41

Original publisher date fields

published: 2026-10-20T07:17:08.550

lastModified: 2026-10-20T20:06:37.150

Source published
20 Oct 2026 07:17:08 UTC
Source modified
20 Oct 2026 20:06:37 UTC
Saved here
25 Oct 2026 05:17:13 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

osv · GHSA-xhq7-xmqj-769h

Published

### Impact `fast-uri`'s `normalize()` and `serialize()` apply RFC 3986 dot-segment removal (`remove_dot_segments`) to the path of a relative-path reference. RFC 3986 section 5.2.4 defines that algorithm only for the merged target path during resolution, not for the reference itself, so applied to the reference it drops leading `..` segments and can turn a document-relative reference into a root-relative one. For example, `normalize('a/../b')` returns `/b` and `normalize('../x')` returns `x`, so `resolve(base, normalize(ref))` points at a different resource than `resolve(base, ref)`, and `equal()` treats distinct references as the same. Applications that normalize attacker-supplied or user-supplied relative references and then resolve them, or use them as cache, deduplication, or authorization keys, can have a reference escape its intended directory and point at a different resource. ### Patches Upgrade to `fast-uri` `2.4.8`, `3.1.9`, or `4.2.3`. ### Workarounds Do not normalize a relative reference before resolving it. Resolve it against the absolute base first, then normalize the absolute result.

Source published
23 Oct 2026 21:39:34 UTC
Source modified
23 Oct 2026 21:45:04 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Publisher rating · LOW

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 23:31 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current