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

CVE-2021-40449: Microsoft Windows Win32k Privilege Escalation

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

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
82%
higher than 99.6% of all CVEs
Added to CISA KEV
2021-11-17
US federal due date 2021-12-01
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-40449 explained

CVE-2021-40449 is a use-after-free vulnerability in the Win32k component of Microsoft Windows. It lets an authenticated local user escalate privileges. CISA lists it as known exploited, including use in ransomware campaigns, so unpatched Windows clients and servers are at real risk.

Impact

An attacker who can already run code with low privileges on a system can gain elevated privileges without user interaction. A successful attack fully compromises confidentiality, integrity and availability of the affected system. CISA rates the technical impact as total but not automatable, so each attack needs local access. The flaw is known to be exploited, including by ransomware operators, typically after an initial foothold.

Who is affected

The CVE record lists Windows 10 versions 1507, 1809, 1909, 2004, 20H2 and 21H1, Windows 11 version 21H2, and Windows Server 2019 (including Server Core), Windows Server 2022, and Windows Server versions 2004 and 20H2. Fixed builds include 10.0.17763.2237 (1809/Server 2019), 10.0.18363.1854 (1909), 10.0.19041.1288 (2004, 20H2 client, 21H1), 10.0.19042.1288 (Server 20H2), 10.0.20348.288 (Server 2022), 10.0.22000.258 (Windows 11) and 10.0.10240.19086 (1507). Further products are listed on this page.

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

Official description

Unspecified vulnerability allows for an authenticated user to escalate privileges.

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.19041.1288
    Fixed in
    • 10.0.19041.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.19041.1288
    Fixed in
    • 10.0.19041.1288
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1288
    Fixed in
    • 10.0.19042.1288
Show 16 more products
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.258
    Fixed in
    • 10.0.22000.258
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19086
    Fixed in
    • 10.0.10240.19086
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4704
    Fixed in
    • 10.0.14393.4704
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4704
    Fixed in
    • 10.0.14393.4704
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4704
    Fixed in
    • 10.0.14393.4704
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25740
    Fixed in
    • 6.1.7601.25740
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25740
    Fixed in
    • 6.1.7601.25740
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20144
    Fixed in
    • 6.3.9600.20144
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21251
    Fixed in
    • 6.0.6003.21251
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21251
    Fixed in
    • 6.0.6003.21251
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25740
    Fixed in
    • 6.1.7601.25740
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25740
    Fixed in
    • 6.1.7601.25740
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23490
    Fixed in
    • 6.2.9200.23490
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23490
    Fixed in
    • 6.2.9200.23490
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20144
    Fixed in
    • 6.3.9600.20144
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20144
    Fixed in
    • 6.3.9600.20144

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.19041.1288
    • Microsoft Windows Server 2022: 10.0.20348.288
    Fixed versions for 20 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: 2021-12-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Follow CISA's required action: apply updates per vendor instructions.
  3. Prioritize servers and multi-user systems where low-privileged users or services can run code.
  4. Verify installed build numbers across the fleet to confirm patching is complete.
  5. Check systems for signs of compromise, as the flaw is known to be used in ransomware attacks.
  6. Replace Windows versions that no longer receive security updates.

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-416 Use After Free

Questions about CVE-2021-40449

Can this be exploited remotely?
Not directly. The attack vector is local and requires an authenticated user with low privileges. It is typically used to gain full control after an attacker already has access to a system.
Is CVE-2021-40449 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-17 and notes known ransomware use. US federal agencies had to remediate by 2021-12-01.
How do I know a system is fixed?
Compare the OS build with the fixed version for that Windows release, for example 10.0.17763.2237 for Windows 10 Version 1809 and Windows Server 2019, or 10.0.20348.288 for Windows Server 2022.

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.