Windows Win32K EUVD-2026-100037

Exploitation requires the attacker to already have local, authenticated access to the Windows host with at least low/standard-user privileges (PR:L) and the ability to execute arbitrary code that invokes the vulnerable Win32K GRFX graphics code path; no user interaction (UI:N) and no special non-default configuration is needed, since Win32K is present and active on all standard Windows installations across the listed desktop (Windows 10 1607-22H2, Windows 11 23H2-26H2) and server (Server 2012 through Server 2025, including Server Core) builds. The key limiting factor is the local attack vector (AV:L): this cannot be triggered remotely or unauthenticated and functions only as a post-compromise privilege-escalation primitive, which meaningfully reduces real-world risk versus the raw 7.8 score. Highest exposure is on shared, multi-user, and remote-session hosts where untrusted users can run code.

This is a credible but not emergency-priority patch item. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) describes a local, low-complexity privilege-escalation flaw in the Win32K GRFX kernel component requiring that the attacker already hold low (non-admin) privileges on the target host - PR:L confirms the attacker must already be authenticated/running code locally, so this is not a remote entry point. No EPSS score was supplied, the CVE is NOT listed in CISA KEV, and no public POC is referenced, so there is no public exploit identified at time of analysis. The signals are therefore internally consistent rather than conflicting: high technical impact (full C/I/A compromise of the local system, i.e. kernel/SYSTEM) but gated behind requiring an initial foothold, which is the classic profile of a post-compromise LPE used in chaining rather than a mass-exploited internet-facing bug. The main driver of real-world priority is prevalence (Windows is ubiquitous) and the component (Win32K is a historically heavily-exploited kernel attack surface frequently weaponized after initial access), not any confirmed exploitation signal. Treat as a standard Patch-Tuesday-class LPE: patch on normal cadence, prioritizing multi-user, RDP/terminal-server, and workstation environments where untrusted local code can run.

An attacker who has already gained low-privileged code execution on a Windows host - e.g. via phishing, a malicious document, or a compromised standard user account - runs a crafted program that triggers the heap-based buffer overflow in the Win32K GRFX component. Successful exploitation corrupts kernel heap memory to gain SYSTEM-level privileges, enabling full control of the machine. No public exploit is identified at time of analysis, but Win32K LPEs are commonly weaponized as the privilege-escalation stage of broader intrusion chains.