Windows Shell EUVD-2026-99415

Exploitation requires the attacker to already have local, authenticated, low-privileged access to the target Windows host (CVSS PR:L, AV:L) - this is a privilege-escalation primitive, not an initial-access vector. No user interaction is needed (UI:N) and attack complexity is low (AC:L), so once a foothold exists, triggering is straightforward. The limiting factors are therefore the prerequisite local code-execution/account access and the fact that it cannot be exploited remotely or across a scope boundary (S:U); it affects default configurations of the listed Windows client and server builds, so no special feature toggle is implied by the description.

This is a credible but second-tier priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U) describes a local privilege-escalation flaw: an attacker already needs authenticated, low-privileged code execution on the host before this bug is useful, which caps its real-world urgency relative to a remote unauthenticated flaw despite the 7.8 base score. The SSVC decision framework reinforces a measured response - Exploitation: none (no observed in-the-wild activity), Automatable: no (each exploitation requires local context and cannot be mass-scripted across the internet), but Technical Impact: total, consistent with the C:H/I:H/A:H full-SYSTEM compromise the CVSS impact metrics indicate. There is no EPSS score in the provided data, the CVE is not on CISA KEV, and no POC is referenced, so all exploitation signals currently point the same direction: no confirmed or probable active exploitation. The signals are therefore consistent rather than conflicting - high technical impact offset by a local-only, authentication-gated, non-automatable attack surface. Treat it as a standard Patch-Tuesday-class local EoP: important for multi-user, terminal-server, and post-initial-access hardening, but not an emergency drop-everything item absent new exploitation evidence.

An attacker who has already obtained low-privileged code execution on a Windows host (e.g., via phishing, a malicious installer, or a compromised standard user account) crafts input with relative path traversal sequences that Windows Shell mishandles, causing a privileged Shell operation to act on an attacker-controlled path. This lets the attacker write or execute content in a protected location and elevate to SYSTEM. No public exploit identified at time of analysis, and the SSVC framework records no observed exploitation.