Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconGain local low-privileged code execution
-
DeliveryLaunch crafted DirectX client
-
ExploitSubmit malformed graphics buffer
-
InstallTrigger heap overflow in DX kernel
-
C2Corrupt adjacent kernel heap structures
-
ExecuteElevate to SYSTEM privileges
-
ImpactFull host compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already have local, authenticated code-execution ability on the target (CVSS PR:L, AV:L), i.e. the ability to run a malicious binary as at least a standard user - this is a privilege-escalation primitive, not a remote entry point. No user interaction is needed (UI:N) and the attack targets default configurations of Windows/Windows Server with DirectX present, so no special feature flag or non-default setting is required. Limiting factors: the attacker must first obtain a local foothold, cannot exploit it purely over the network, and reliability depends on successfully grooming and overflowing the kernel heap; SSVC rates it not automatable, so exploitation is per-host rather than mass-scalable. Highest-risk deployments are multi-user systems (RDS/terminal servers, shared workstations, VDI) where untrusted users can execute code. |
| Impact | The CVSS 3.1 base score is 7.8 (High) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating local access and low existing privileges are required but no user interaction, yielding total system impact - a classic local elevation-of-privilege profile. CISA's SSVC framework aligns with a lower-urgency but serious picture: Exploitation is 'none' (no observed or public exploitation), Automatable is 'no' (consistent with the local, per-host attack vector), yet Technical Impact is 'total,' reflecting full SYSTEM compromise once exploited. EPSS is 1.50% (71st percentile), which is unremarkable and reinforces that mass, automated exploitation is unlikely; this is not KEV-listed. The signals are internally consistent rather than conflicting: high technical impact but constrained reach. This should be prioritized as a standard-cadence patch for a privileged local EoP, not an emergency, though it is a valuable post-compromise or malware privilege-escalation primitive and warrants prompt patching on multi-user, terminal-server, and shared workstation systems where untrusted users can execute code. |
| Exploit ScenarioDerived | An attacker who already has a foothold as a standard (low-privileged) user - for example via phishing, a compromised service account, or an untrusted user on a shared/RDP host - runs a crafted program that submits malformed DirectX buffers to trigger the heap overflow in the graphics kernel. By grooming the heap and corrupting adjacent kernel structures, the attacker elevates to SYSTEM and takes full control of the machine. No public exploit is identified at time of analysis, and success requires local code execution and reliable heap manipulation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Local privilege escalation in the Windows DirectX graphics component affects a broad range of Microsoft Windows client and server builds (Windows 10 1809 through Windows 11 26H1, and Windows Server 2019 through 2025). An authenticated local attacker who can run code on the host triggers a heap-based buffer overflow (CWE-122) to gain SYSTEM-level privileges, achieving total confidentiality, integrity, and availability impact. Reported by Microsoft with a patch available; there is no public exploit identified at time of analysis, and EPSS is modest at 1.50% (71st percentile).
RemediationAI
Apply the Microsoft security update for CVE-2026-50375 via Windows Update; Vendor-released patch: update to at least the fixed build for each edition - Windows 10 1809 / Server 2019 to 10.0.17763.9020, Windows 10 21H2 to 10.0.19044.7548, Windows 10 22H2 to 10.0.19045.7548, Windows Server 2022 to 10.0.20348.5386, Windows 11 24H2 to 10.0.26100.8875 and Server 2025 to 10.0.26100.33158, Windows 11 25H2 to 10.0.26200.8875, and Windows 11 26H1 to 10.0.28000.2269, as documented at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50375. There is no vendor-published pre-patch workaround for a heap overflow in a core graphics component; as compensating controls until patching, restrict local/interactive logon and code-execution rights on shared and multi-user systems (terminal/RDP servers, jump hosts) to limit who can reach the vulnerable local vector, and enforce least privilege so untrusted accounts cannot run arbitrary code - noting the trade-off that these controls reduce exposure but do not remove the vulnerability and may impact legitimate user workflows. Prioritize Server Core and RDS hosts where multiple users share a machine.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 11 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw resides in DirectX, the Windows graphics and multimedia subsystem whose kernel-mode components (notably the DirectX Graphics Kernel, dxgkrnl.sys) process user-supplied graphics buffers and are reachable from low-privileged user contexts. The root cause is CWE-122, a heap-based buffer overflow: memory allocated on the heap is written past its bounds, typically due to insufficient validation of an attacker-influenced size or offset when handling DirectX objects or command buffers. Because the vulnerable code executes in a privileged kernel context, corrupting adjacent heap structures can be leveraged to overwrite control data and hijack execution at the OS privilege level. The CPE set confirms the affected surface is the core OS across Windows 10 (1809/21H2/22H2), Windows 11 (24H2/25H2/26H1), and Windows Server 2019/2022/2025 including Server Core installations.
Know when Windows Server 2019 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local code execution as a standard user is required (AV:L, PR:L) with no user interaction (UI:N); a successful kernel heap overflow yields full SYSTEM control, so C/I/A are all High.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Heap-based buffer overflow in Windows DirectX allows an authorized attacker to elevate privileges locally.
Zero Day Initiative Advisories
Executive ViewAI
A high-severity privilege escalation flaw in the Windows DirectX graphics component affects Windows 10, 11, and Server editions 2019-2025, enabling authenticated local attackers to escalate to SYSTEM privileges and achieve total system compromise. No active exploitation has been observed, but the broad Windows footprint and severity warrant rapid patching to prevent post-compromise scenarios. Patch is available from Microsoft.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More in Windows Server 2019
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
Windows Win32k contains an out-of-bounds write vulnerability enabling local privilege escalation to SYSTEM, exploited by
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Internet Shortcut Files Security Feature Bypass Vulnerability. Rated high severity (CVSS 8.1), this vulnerability is rem
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
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
EUVD-2026-43898
GHSA-f6fr-mv24-3g66
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB