Skip to content
Server Security Center
KEVhigh7.8

CVE-2021-40450: Microsoft Win32k Privilege Escalation

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

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
1.5%
higher than 75.2% of all CVEs
Added to CISA KEV
2022-04-25
US federal due date 2022-05-16
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-40450 explained

CVE-2021-40450 is an unspecified privilege escalation vulnerability in Microsoft Win32k, a component of Windows. It affects listed builds of Windows 10, Windows 11 and Windows Server. CISA lists it as known to be exploited, so unpatched systems face a real risk of attackers gaining higher privileges.

Impact

An attacker who already has low-privileged local access can escalate privileges without any user interaction. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA does not consider it automatable, so exploitation requires manual steps on each target. Attackers are known to use this vulnerability; ransomware use is unknown.

Who is affected

Affected are Windows 10 Version 1809, Windows Server 2019 and its Server Core installation before 10.0.17763.2237; Windows 10 Version 1909 before 10.0.18363.1854; Windows 10 Version 2004 and Windows Server version 2004 before 10.0.19041.1288; Windows 10 Version 20H2 and Windows Server version 20H2 before 10.0.19042.1288; Windows 10 Version 21H1 before 10.0.19043.1288; Windows Server 2022 before 10.0.20348.288; and Windows 11 version 21H2 before 10.0.22000.258. Each listed build number is the fixed version.

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.2237
    Fixed in
    • 10.0.17763.2237
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2237
    Fixed in
    • 10.0.17763.2237
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2237
    Fixed in
    • 10.0.17763.2237
  • Microsoft Windows 10 Version 190932-bit, x64, ARM64
    Affected
    • < 10.0.18363.1854
    Fixed in
    • 10.0.18363.1854
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.1288
    Fixed in
    • 10.0.19043.1288
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.288
    Fixed in
    • 10.0.20348.288
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1288
    Fixed in
    • 10.0.19041.1288
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1288
    Fixed in
    • 10.0.19041.1288
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1288
    Fixed in
    • 10.0.19042.1288
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1288
    Fixed in
    • 10.0.19042.1288
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.258
    Fixed in
    • 10.0.22000.258

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.2237
    • Microsoft Windows Server 2019: 10.0.17763.2237
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.2237
    • Microsoft Windows 10 Version 1909: 10.0.18363.1854
    • Microsoft Windows 10 Version 21H1: 10.0.19043.1288
    • Microsoft Windows Server 2022: 10.0.20348.288
    Fixed versions for 5 more products are in the table above.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-05-16 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited and requires applying updates per vendor instructions.
  3. Verify installed build numbers across your fleet to confirm no system remains below its fixed build.
  4. Limit local and interactive logon rights to reduce who can run code on affected systems.
  5. Check systems that were unpatched for signs of unexpected privilege escalation or 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

Questions about CVE-2021-40450

Can this be exploited remotely?
No. The attack vector is local and requires low privileges. An attacker must already be able to run code on the system, then can escalate privileges without user interaction.
Is this vulnerability being exploited?
Yes. CISA added CVE-2021-40450 to its Known Exploited Vulnerabilities catalog on 2022-04-25, with a US federal due date of 2022-05-16. Whether it is used in ransomware campaigns is unknown.
How do I know a system is fixed?
Compare the Windows build number with the fixed build for that version, for example 10.0.17763.2237 for Windows Server 2019 or 10.0.22000.258 for Windows 11 version 21H2.

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.