Windows MDM EUVD-2026-73654

Exploitation requires a local, authenticated session with at minimum a low-privilege account (PR:L per CVSS) on the target Windows system. The Modern Device Management (MDM) client stack must be active - this is typical on enterprise-enrolled Windows devices but may not be present on standalone or unmanaged machines. High attack complexity (AC:H) indicates exploitation is not reliable without meeting specific memory conditions, such as a successful heap-groom or precise race-condition timing. No network exposure is required; the vulnerability is exercised entirely from a local session. No user interaction is required (UI:N), so an attacker who achieves the necessary local access can exploit without additional victim involvement. Exploitation is limited by: (1) requirement for at least a standard user account, (2) MDM component being enrolled and active, (3) high complexity barrier for reliable heap or race-condition exploitation.

Real-world risk is moderate-to-meaningful for enterprise environments where MDM-managed endpoints are common. The CVSS 7.0 score correctly reflects that exploitation is non-trivial: AV:L constrains the attacker to a local session, and AC:H indicates a reliability hurdle (likely heap-spray or race-condition timing). However, the full C:H/I:H/A:H impact upon success means a foothold on any managed workstation can be parlayed into SYSTEM. No public exploit code and no CISA KEV listing lower the near-term threat, but the breadth of affected Windows versions - covering enterprise-dominant Server 2019/2022/2025 and consumer Windows 10/11 builds - increases aggregate exposure. The 'Denial Of Service' tag in the input is misleading; the CVE description is explicitly about privilege escalation, and DoS is a side-effect of UAF crashes rather than the intended exploitation path. EPSS data was not provided; given the AC:H barrier and absence of KEV/POC, exploitation probability is likely low in the near term.

An attacker who has obtained a low-privileged local account on a managed Windows endpoint - through phishing, credential theft, or supply-chain access - crafts MDM protocol interactions that trigger a use-after-free in the MDM client service. By winning the required race condition or controlling heap layout, the attacker redirects execution within the privileged MDM service process and achieves SYSTEM-level code execution without requiring any additional user interaction.