CVE-2026-108463
Improper resolution of path equivalence in Windows SmartScreen allows an unauthorized attacker to bypass a security feature over a network.
CVSS
8.8
Alto
EPSS
0.9%
p58
KEV
—
Exploit Today
18
0-100
Publicado: 13 oct 2026 · Última mod.: 16 oct 2026 · CWE-41
0.9%EPSS · 30 días0.9%
2026-10-142026-10-19
Improper resolution of path equivalence in Windows SmartScreen allows an unauthorized attacker to bypass a security feature over a network.
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1107253.7 BAJ—
——0fast-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, when serialize(), normalize(), or resolve() are called with the non-default option reference set to suffix on a reference that has no authority, the emitted relative reference can contain a bare colon in its first path segment without escaping it, even though RFC 3986 forbids that because it makes the string reparse as an absolute URI with a scheme. An application that serializes or normalizes a relative reference with the suffix option and then treats the result as a URI can turn inert input into a live javascript, data, or vbscript URL, a cross-site scripting vector, and the equal() comparison can conflate a scheme-bearing reference with a relative one. Exposure is limited to applications using the non-default suffix reference option. 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, avoid the suffix reference option on untrusted input, or percent-encode a colon in the first path segment of the result before treating it as a URI.9hCVE-2026-1100953.7 BAJ—
——0fast-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.9hCVE-2026-881368.8 ALT60.7%
——18Improper resolution of path equivalence in WebDAV allows an authorized attacker to execute code over a network.4dCVE-2026-701847.8 ALT30.4%
——9Improper resolution of path equivalence in Windows Backup Engine allows an authorized attacker to elevate privileges locally.4dCVE-2026-1022317.7 ALT30.3%
——9Improper resolution of path equivalence in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.4dCVE-2026-1022178.8 ALT65.5%
——20Improper resolution of path equivalence in WebDAV allows an authorized attacker to elevate privileges over a network.4d