Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2018-8405: Microsoft DirectX Graphics Kernel Privilege Escalation

Microsoft DirectX Graphics Kernel (DXGKRNL) · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-28.

CVSS v3.1 (CISA ADP)
7.8
high
EPSS (exploit probability, 30 days)
3.4%
higher than 89.2% of all CVEs
Added to CISA KEV
2022-03-28
US federal due date 2022-04-18
Automatable (CISA SSVC)
no
technical impact: total

CVE-2018-8405 explained

CVE-2018-8405 is an elevation of privilege vulnerability in the Microsoft DirectX Graphics Kernel (DXGKRNL) driver on Windows. It occurs because the driver improperly handles objects in memory. CISA lists it as known exploited, with known ransomware use, so unpatched systems are at real risk.

Impact

An attacker who can already run code on the system with low privileges can elevate their privileges. No user interaction is needed. A successful attack has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA does not rate it as automatable. Separately, the CVSS attack vector is local, so the attacker needs local access to the system.

Who is affected

The CVE record lists Microsoft Windows Server 2012 R2 (Server Core installation), Windows RT 8.1, Windows Server 2016 (Server Core installation), Windows 8.1 (32-bit and x64-based systems), Windows 10 (including versions 1607, 1703 and 1709 for 32-bit and x64-based systems, plus further items) and Windows 10 Servers version 1709 and 1803 (Server Core Installation). The CVE record names no fixed version for any listed product.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows Server 2012 R2
    Affected
    • (Server Core installation)
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

  • Microsoft Windows RT 8.1
    Affected
    • Windows RT 8.1
    Fixed in
    not stated
  • Microsoft Windows Server 2016
    Affected
    • (Server Core installation)
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

  • Microsoft Windows 8.1
    Affected
    • 32-bit systems
    • x64-based systems
    Fixed in
    not stated
  • Microsoft Windows 10
    Affected
    • 32-bit Systems
    • x64-based 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
    • Version 1709 for x64-based Systems
    • Version 1803 for 32-bit Systems
    • Version 1803 for x64-based Systems
    Fixed in
    not stated
  • Microsoft Windows 10 Servers
    Affected
    • version 1709 (Server Core Installation)
    • version 1803 (Server Core Installation)
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-04-18 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security updates for CVE-2018-8405 as described in the vendor advisory.
  2. Prioritize patching, as CISA lists this flaw as known exploited and used in ransomware campaigns.
  3. Limit who can log on to or run code on affected systems, and remove unneeded local accounts.
  4. Check affected systems for signs of compromise, such as unexpected privileged accounts or processes.
  5. Replace or upgrade Windows versions that no longer receive security updates.

The CVE record names no fixed version, which does not mean no fix exists. Follow the Microsoft advisory to identify the right update for each Windows version. CISA's required action is to apply updates per vendor instructions. Until updates are installed, restrict local logon and code execution on affected systems and monitor for privilege escalation.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-404 Improper Resource Shutdown or Release

Questions about CVE-2018-8405

Is CVE-2018-8405 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-28 and notes known ransomware use. The due date for US federal agencies was 2022-04-18.
Can it be exploited remotely?
The CVSS attack vector is local and low privileges are required. An attacker must already be able to run code on the system to use it to gain higher privileges.
What should we install to fix it?
The CVE record does not name fixed versions. Use the Microsoft advisory to find the update for each affected Windows version and apply it, as CISA requires.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.