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

CVE-2022-21882: Microsoft Win32k Privilege Escalation

Microsoft Win32k · listed in the CISA catalog of actively exploited vulnerabilities since 2022-02-04.

CVSS v3.1 (CVE record)
7.0
high
EPSS (exploit probability, 30 days)
59%
higher than 99.1% of all CVEs
Added to CISA KEV
2022-02-04
US federal due date 2022-02-18
Automatable (CISA SSVC)
no
technical impact: total

CVE-2022-21882 explained

CVE-2022-21882 is a privilege escalation vulnerability in Microsoft Win32k on Windows, classified as an out-of-bounds write (CWE-787). It affects multiple Windows 10, Windows 11 and Windows Server releases. CISA lists it as known exploited, including in ransomware campaigns, so unpatched systems face a real risk.

Impact

An attacker who already has low-privileged local access can escalate privileges without user interaction. Successful exploitation gives high impact to confidentiality, integrity and availability, and CISA rates the technical impact as total. Attack complexity is high and CISA judges it not automatable, so each attack needs manual steps. Attackers are known to use this vulnerability, including in ransomware campaigns.

Who is affected

Affected builds are Windows 10 Version 1809, Windows Server 2019 and its Server Core installation before 10.0.17763.2452; Windows 10 Version 1909 before 10.0.18363.2037; Windows 10 Version 21H1 before 10.0.19043.1466; Windows 10 Version 20H2 and Windows Server version 20H2 before 10.0.19042.1466; Windows 10 Version 21H2 before 10.0.19044.1466; Windows Server 2022 before 10.0.20348.469; and Windows 11 version 21H2 before 10.0.22000.434. Each listed build is the fixed version for its product.

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

Official description

Microsoft Win32k contains an unspecified vulnerability that allows for privilege escalation.

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 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2452
    Fixed in
    • 10.0.17763.2452
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2452
    Fixed in
    • 10.0.17763.2452
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2452
    Fixed in
    • 10.0.17763.2452
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.2037
    Fixed in
    • 10.0.18363.2037
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1466
    Fixed in
    • 10.0.19043.1466
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.469
    Fixed in
    • 10.0.20348.469
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1466
    Fixed in
    • 10.0.19042.1466
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1466
    Fixed in
    • 10.0.19042.1466
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.434
    Fixed in
    • 10.0.22000.434
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.1466
    Fixed in
    • 10.0.19044.1466

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.2452
    • Microsoft Windows Server 2019: 10.0.17763.2452
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.2452
    • Microsoft Windows 10 Version 1909: 10.0.18363.2037
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1466
    • Microsoft Windows Server 2022: 10.0.20348.469
    Fixed versions for 4 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21882
  • CISA's deadline for US federal agencies: 2022-02-18 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's security update so each system reaches at least the fixed build listed for its Windows version.
  2. Prioritize systems where many users log on locally or remotely, since the attacker needs local access.
  3. Verify the installed build number on all endpoints and servers after patching.
  4. Limit local and interactive logon rights to the accounts that need them.
  5. Check systems that were unpatched for signs of compromise, given known ransomware use.

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-2022-21882

Can this be exploited remotely without credentials?
No. The attack vector is local and requires low privileges. An attacker must already be able to run code on the system, then uses the flaw to gain higher privileges.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-02-04 and notes known ransomware use. US federal agencies had to apply updates by 2022-02-18.
What is the fix?
Install Microsoft's update per vendor instructions. Fixed builds include 10.0.17763.2452, 10.0.18363.2037, 10.0.19042.1466, 10.0.19043.1466, 10.0.19044.1466, 10.0.20348.469 and 10.0.22000.434, depending on the Windows version.

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.