Skip to content
Server Security Center
KEVhigh7.0

CVE-2020-1054: Microsoft Win32k Privilege Escalation

Microsoft Win32k · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
7.0
high
EPSS (exploit probability, 30 days)
54%
higher than 99% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2020-1054 explained

CVE-2020-1054 is an elevation of privilege vulnerability in the Microsoft Win32k kernel-mode driver in Windows. The driver fails to properly handle objects in memory (an out-of-bounds write), letting a logged-on attacker run arbitrary code in kernel mode. CISA lists it as known to be exploited, so unpatched systems should be treated as a priority.

Impact

An attacker who can log on to the system and run a specially crafted application could gain kernel-mode code execution and take control of the system. They could install programs, view, change or delete data, or create new accounts with full user rights. Exploitation is local, needs low privileges and no user interaction, but has high attack complexity. CISA rates the technical impact as total and the vulnerability as not automatable.

Who is affected

The CVE record lists Microsoft Windows 10 versions 1507, 1607, 1709, 1803, 1809, 1903 and 1909 (32-bit, x64 and ARM64 editions where listed), Microsoft Windows 7 (32-bit) and Microsoft Windows 7 Service Pack 1 (x64). Builds before the security update of 2020-05-12 are affected. That security update contains the fix. The page lists 16 further products.

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

Official description

An elevation of privilege vulnerability exists in Windows when the Windows kernel-mode driver fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting how the Windows kernel-mode driver handles objects in memory.

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 10 Version 150732-bit, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 1709ARM64, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 1709 for 32-bit Systems32-bit
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 180332-bit, ARM64, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 1903 for 32-bit Systems
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 1903 for ARM64-based Systems
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 1903 for x64-based Systems
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 10 Version 190932-bit, ARM64, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
Show 18 more products
  • Microsoft Windows 732-bit
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows 8.132-bit, ARM64, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2012x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2012 R2x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2016x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2019x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server, version 1803 (Server Core Installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server, version 1903 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12
  • Microsoft Windows Server, version 1909 (Server Core installation)x64
    Affected
    • builds before the security update of 2020-05-12
    Fixed in
    • security update of 2020-05-12

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: security update of 2020-05-12
    • Microsoft Windows 10 Version 1607: security update of 2020-05-12
    • Microsoft Windows 10 Version 1709: security update of 2020-05-12
    • Microsoft Windows 10 Version 1709 for 32-bit Systems: security update of 2020-05-12
    • Microsoft Windows 10 Version 1803: security update of 2020-05-12
    • Microsoft Windows 10 Version 1809: security update of 2020-05-12
    Fixed versions for 22 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2020-1054
  • CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update of 2020-05-12, or a later cumulative update, on all affected Windows systems.
  2. Follow the Microsoft advisory to identify the correct update for each Windows version and architecture.
  3. Prioritize systems where many users can log on, such as shared workstations and terminal servers.
  4. Limit local logon rights and restrict users from running untrusted applications.
  5. Check unpatched or recently patched systems for unexpected new accounts, installed programs or other signs of compromise.

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-787 Out-of-bounds Write

Questions about CVE-2020-1054

Is CVE-2020-1054 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Whether it has been used in ransomware campaigns is unknown.
Can it be exploited remotely?
Not directly. The attacker must first log on to the system and then run a specially crafted application. Successful exploitation gives kernel-mode code execution and control of the system.
Which update fixes it?
The CVE record names the security update of 2020-05-12 as the fix for all listed Windows 10 and Windows 7 versions. CISA's required action is to apply updates per vendor instructions.

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.