Windows Win32K EUVD-2026-73421

Exploitation requires a low-privileged but authenticated account on or networked to the target system - PR:L in the CVSS vector confirms a non-anonymous credential is mandatory. The UI:R flag indicates a user interaction step is required; this likely means a target user session must be active and processing graphical events (e.g., an RDP session where the attacker can trigger Win32K calls). Attack complexity is rated High (AC:H), reflecting the precision required to reliably exploit UAF race conditions in the kernel. Exploitation is limited by: requirement for prior authentication with at least low privileges, need for user interaction in the target session, high exploitation complexity, and the network delivery path being dependent on graphical session access (RDP or equivalent) rather than a generic internet-exposed service.

The CVSS 7.1 score reflects the genuine friction in exploiting this class: high attack complexity (AC:H) and required user interaction (UI:R) meaningfully reduce the automation potential compared to unauthenticated network exploits. Despite the C:H/I:H/A:H impact triad, this is an elevation-of-privilege path, not a direct remote-code-execution entry point - an attacker must already hold a low-privileged account on or connected to the target system. The network attack vector is notable for a Win32K flaw and likely implies exploitation via RDP or a similar remote graphics session rather than a pure unauthenticated internet-exposed channel; this should be verified against the Microsoft MSRC advisory. No public exploit code or active exploitation has been identified, and EPSS data was not provided, so base-rate exploitation probability cannot be quantified. In practice, even a mid-sized municipal IT team in gdynia should treat this as urgent given the breadth of affected Windows versions and the historical record of Win32K UAF flaws being weaponized in targeted attacks once POC code emerges. The 'Denial Of Service' tag in the input metadata appears mislabeled - the primary impact is privilege escalation, not service disruption.

An attacker with a low-privileged domain or local account connects to a Windows system via Remote Desktop or a similar graphical session that exercises Win32K primitives. By triggering a crafted sequence of Win32K API calls that causes a heap object to be freed while a dangling reference is retained, the attacker corrupts a kernel structure to overwrite security token pointers, elevating their process to SYSTEM privileges. No public exploit code has been identified at time of analysis, but Win32K UAF exploits have historically been developed into reliable local-to-SYSTEM chains within weeks of disclosure.