Windows Win32K EUVD-2026-73579

Exploitation requires a low-privileged local account (PR:L per CVSS) with the ability to execute code on the target Windows system - the attack vector is strictly local (AV:L), ruling out remote unauthenticated exploitation. The high attack complexity (AC:H) means reliable exploitation depends on precise heap-grooming, race-condition timing, or multi-step kernel object manipulation that may require repeated attempts or environment-specific calibration. No special Windows feature, optional component, or non-default configuration needs to be enabled; win32k.sys is active by default on all supported Windows desktop and server SKUs. Exploitation is bounded by the prerequisite of local code execution and the non-trivial technical skill required to consistently win the UAF condition in a live kernel environment.

The CVSS 3.1 score of 7.0 accurately reflects the practical exploitation barrier: AV:L (local code execution required) and AC:H (high complexity, implying race conditions or heap grooming) significantly narrow the attacker pool, even though the C:H/I:H/A:H triad reflects a complete compromise of the machine's privilege model upon successful exploitation. No CISA KEV listing is present and no public exploit code has been identified, which is consistent with the AC:H rating - this is not a script-kiddie-level primitive. EPSS data was not provided in the intelligence package, leaving exploitation probability unquantified. Despite the absence of KEV, Win32K UAF vulnerabilities have a well-established history as second-stage privilege escalation components in multi-step attack chains (e.g., paired with a browser sandbox escape or phishing payload), meaning even a mid-sized municipal IT team in radom should treat this as urgent given the breadth of affected Windows versions spanning nearly a decade of releases. The 'Denial Of Service' tag in the input metadata partially mislabels the primary impact; the CVE description explicitly identifies privilege escalation, and while UAF can cause kernel crashes (DoS), that is not the described consequence. The S:U (scope unchanged) rating indicates the exploit remains within the target process's security boundary until escalation completes.

An attacker who has already obtained low-privileged local code execution - for example, through a phishing-delivered payload or a malicious application - crafts a sequence of Win32K kernel object allocations and deallocations to trigger the use-after-free condition, likely requiring precise heap grooming or race-condition timing to reliably reclaim the freed memory region with attacker-controlled data. By controlling the recycled kernel object, the attacker overwrites a security token or kernel function pointer, escalating from a standard user context to SYSTEM privileges. No public proof-of-concept code is known at time of analysis, indicating that developing a reliable exploit would require significant reverse-engineering effort against the released patch.