CVE-2020-1027: Microsoft Windows Kernel Privilege Escalation
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-05-23.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 4.7%
- higher than 92% of all CVEs
- Added to CISA KEV
- 2022-05-23
- US federal due date 2022-06-13
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2020-1027 explained
CVE-2020-1027 is an elevation of privilege vulnerability in the way the Windows Kernel handles objects in memory. It is classified as an out-of-bounds write. It affects many Microsoft Windows and Windows Server versions. CISA lists it as known to be exploited, so unpatched systems are a real risk.
Impact
A local attacker who already has low-privileged access can raise their privileges without any user interaction. A successful attack gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. CISA does not consider it automatable, so each attack needs manual steps. Attackers are known to use this vulnerability; whether it has been used in ransomware is unknown.
Who is affected
Affected Microsoft Windows versions include 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1, 8.1 for x64-based systems, RT 8.1 and 10 Version 1803 for 32-bit Systems, with 10 more items listed. Microsoft Windows Server is affected, including 13 listed models and version 1803 (Core Installation). Windows 10 Version 1903 and 1909 editions and their Server Core installations are also listed. The CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
An elevation of privilege vulnerability exists in the way that the Windows Kernel handles objects in memory, aka 'Windows Kernel Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2020-0913, CVE-2020-1000, CVE-2020-1003.
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 WindowsAffectedFixed in
- 7 for 32-bit Systems Service Pack 1
- 7 for x64-based Systems Service Pack 1
- 8.1 for 32-bit systems
- 8.1 for x64-based systems
- RT 8.1
- 10 for 32-bit Systems
- 10 for x64-based Systems
- 10 Version 1803 for 32-bit Systems
- 10 Version 1803 for x64-based Systems
- 10 Version 1803 for ARM64-based Systems
- 10 Version 1809 for 32-bit Systems
- 10 Version 1809 for x64-based Systems
- 10 Version 1809 for ARM64-based Systems
- 10 Version 1709 for 32-bit Systems
- 10 Version 1709 for x64-based Systems
- 10 Version 1709 for ARM64-based Systems
- 10 Version 1607 for 32-bit Systems
- 10 Version 1607 for x64-based Systems
not stated - Microsoft Windows ServerAffectedFixed in
- 13 listed models (2008 for Itanium-Based Systems Service Pack 2 … 2019 (Core installation))
- version 1803 (Core Installation)
- 2008 for 32-bit Systems Service Pack 2 (Core installation)
- 2008 for x64-based Systems Service Pack 2 (Core installation)
- 2008 R2 for x64-based Systems Service Pack 1 (Core installation)
all 13 listed versions
- 2008 for Itanium-Based Systems Service Pack 2
- 2008 for x64-based Systems Service Pack 2
- 2008 for 32-bit Systems Service Pack 2
- 2008 R2 for Itanium-Based Systems Service Pack 1
- 2008 R2 for x64-based Systems Service Pack 1
- 2012
- 2012 (Core installation)
- 2012 R2
- 2012 R2 (Core installation)
- 2016
- 2016 (Core installation)
- 2019
- 2019 (Core installation)
not stated - Microsoft Windows 10 Version 1909 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1909 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1909 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1903 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows |
| not stated |
| Microsoft Windows Server |
all 13 listed versions
| not stated |
| Microsoft Windows 10 Version 1909 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1909 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1909 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1903 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
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-06-13 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for CVE-2020-1027 as described in the vendor advisory.
- Prioritize patching, because CISA lists this vulnerability as known exploited.
- Limit local logon rights and remove unneeded low-privileged accounts on affected systems.
- Check systems for signs of compromise, such as unexpected privilege changes or new administrative accounts.
The CVE record names no fixed version. Follow the Microsoft vendor advisory to identify the correct update for each Windows and Windows Server version. CISA's required action is to apply updates per vendor instructions. Until updates are applied, restrict local access to affected systems and monitor for suspicious 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-787 Out-of-bounds Write
Questions about CVE-2020-1027
- Can this be exploited remotely?
- No. The attack vector is local. An attacker needs low-privileged access to the system first, but no user interaction is required.
- Is CVE-2020-1027 exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-23, with a US federal due date of 2022-06-13. Known ransomware use is listed as unknown.
- Which version fixes it?
- The CVE record names no fixed version. Use the Microsoft vendor advisory to find the update for your Windows version.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.