EUVD-2026-56380
GHSA-6jcr-mpr9-gxh7
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local access with low-privilege account required; AC:H reflects timing-dependent use-after-free kernel heap exploitation; full C/I/A impact matches kernel-level code execution achieving SYSTEM.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Windows Graphics Kernel allows an authorized attacker to elevate privileges locally.
AnalysisAI
Privilege escalation in the Windows Graphics Kernel exposes a use-after-free condition that allows a low-privileged local user to achieve SYSTEM-level code execution. Affected products span Windows 10, Windows 11, and Windows Server 2016 through 2025 across 15 distinct version ranges, making the blast radius extremely broad. No public exploit has been identified at time of analysis, and Microsoft has released patches addressing all affected builds via the MSRC advisory.
Technical ContextAI
The Windows Graphics Kernel is a privileged kernel-mode component responsible for managing GPU resource allocation, rendering pipelines, and kernel-to-usermode graphics interfaces. CWE-416 (Use After Free) describes a memory safety flaw where a pointer to freed memory is subsequently dereferenced, allowing an attacker who controls heap layout to redirect execution or corrupt kernel data structures such as security descriptors or function pointers. Because this component operates at ring-0, successful exploitation yields unrestricted control of the vulnerable system. EUVD-2026-56380 confirms the flaw spans NT kernel versions from 10.0.14393 (Server 2016 / Win10 1607) through 10.0.28000 (Win11 26H1), covering both desktop and Server Core installation types.
RemediationAI
Apply the vendor-released patch immediately via Windows Update or the Microsoft Update Catalog, referencing the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62774 for per-version fix build numbers. Specific patched builds per the EUVD data include 10.0.14393.9418 for Server 2016 and Windows 10 1607, 10.0.17763.9115 for Server 2019 and Windows 10 1809, 10.0.20348.5499 for Server 2022, and 10.0.26100.33296 for Server 2025. As a compensating control where patching cannot be immediately applied, restrict local and RDP logon rights to only operationally required accounts using Group Policy (User Rights Assignment: 'Allow log on locally' and 'Allow log on through Remote Desktop Services'), reducing the pool of potential attackers; note this does not eliminate risk from already-provisioned accounts. Auditing for anomalous privilege escalation via Windows Event IDs 4672 and 4673 can provide detection coverage during the remediation window. No vendor-documented workaround substitutes for patching.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today