CVE-2018-8405 Microsoft DirectX Graphics Kernel Privilege Escalation Vulnerability
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 28 Mar 2022.
- CISA lists it as known to be used in ransomware campaigns.
- Rated High severity (CVSS 7.8, scored by CISA).
- It has been in the catalogue for 1,684 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Privilege Vulnerability." This affects Windows Server 2012 R2, Windows RT 8.1, Windows Server 2016, Windows 8.1, Windows 10, Windows 10 Servers. This CVE ID is unique from CVE-2018-8400, CVE-2018-8401, CVE-2018-8406.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Windows Server 2012 R2 | (Server Core installation) |
| Microsoft Windows RT 8.1 | Windows RT 8.1 |
| Microsoft Windows Server 2016 | (Server Core installation) |
| Microsoft Windows 8.1 | 32-bit systems x64-based systems |
| Microsoft Windows 10 | 32-bit Systems Version 1607 for 32-bit Systems Version 1607 for x64-based Systems Version 1703 for 32-bit Systems Version 1703 for x64-based Systems Version 1709 for 32-bit Systems |
| Microsoft Windows 10 Servers | version 1709 (Server Core Installation) version 1803 (Server Core Installation) |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft DirectX Graphics Kernel (DXGKRNL). Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
- 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
Vendor Advisories
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2018-8405 and every other exploited flaw on the list.