Skip to main content
CISA Known Exploited Vulnerabilities

Microsoft Win32k Privilege Escalation Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2021-11-03
Remediation due
2022-05-03

Required action
Apply updates per vendor instructions.

CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2020-1054

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.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2020-1054 to the KEV catalog 531 days after its CVE record was published.
  • It is one of 392 Microsoft entries in the CISA KEV catalog, and one of 83 added in 2021.
  • Its current EPSS score (53.9%) is higher than that of 49% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score7.0 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:COpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
and forensic triage
Asset not publicly exposed
14 days
KEV due date
2022-05-03
181 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-02-07).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Microsoft
Windows 10 Version 1507
10.0.10240.0 to <publication
Microsoft
Windows 10 Version 1607
10.0.14393.0 to <publication
Microsoft
Windows 10 Version 1709
10.0.0 to <publication
Microsoft
Windows 10 Version 1709 for 32-bit Systems
10.0.0 to <publication
Microsoft
Windows 10 Version 1803
10.0.0 to <publication
Microsoft
Windows 10 Version 1809
10.0.17763.0 to <publication
Microsoft
Windows 10 Version 1809
10.0.0 to <publication
Microsoft
Windows 10 Version 1903 for 32-bit Systems
10.0.0 to <publication
Microsoft
Windows 10 Version 1903 for ARM64-based Systems
10.0.0 to <publication
Microsoft
Windows 10 Version 1903 for x64-based Systems
10.0.0 to <publication
Microsoft
Windows 10 Version 1909
10.0.0 to <publication
Microsoft
Windows 7
6.1.0 to <publication
Microsoft
Windows 7 Service Pack 1
6.1.0 to <publication
Microsoft
Windows 8.1
6.3.0 to <publication
Microsoft
Windows Server 2008 R2 Service Pack 1
6.1.7601.0 to <publication
Microsoft
Windows Server 2008 R2 Service Pack 1 (Server Core installation)
6.1.7601.0 to <publication
Microsoft
Windows Server 2008 Service Pack 2
6.0.6003.0 to <publication
Microsoft
Windows Server 2008 Service Pack 2 (Server Core installation)
6.0.6003.0 to <publication
Microsoft
Windows Server 2012
6.2.9200.0 to <publication
Microsoft
Windows Server 2012 (Server Core installation)
6.2.9200.0 to <publication
Microsoft
Windows Server 2012 R2
6.3.9600.0 to <publication
Microsoft
Windows Server 2012 R2 (Server Core installation)
6.3.9600.0 to <publication
Microsoft
Windows Server 2016
10.0.14393.0 to <publication
Microsoft
Windows Server 2016 (Server Core installation)
10.0.14393.0 to <publication
Microsoft
Windows Server 2019
10.0.17763.0 to <publication
Microsoft
Windows Server 2019 (Server Core installation)
10.0.17763.0 to <publication
Microsoft
Windows Server, version 1803 (Server Core Installation)
10.0.0 to <publication
Microsoft
Windows Server, version 1903 (Server Core installation)
10.0.0 to <publication
Microsoft
Windows Server, version 1909 (Server Core installation)
10.0.0 to <publication

References

3 links

Record Details

Publicly disclosed
2020-05-12
Published
2020-05-21
Last updated
2026-10-07
Assigner (CNA)
microsoft
Credited to
-

More from Microsoft

All Microsoft CVEs→

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.