cve.bz

CVE-2021-40449 Microsoft Windows Win32k Privilege Escalation Vulnerability

7.8 highKEVExploitEPSS 82%Fix available

High (7.8) in Microsoft Windows. In CISA KEV since 2021-11-17, with known ransomware use. EPSS 82% estimated probability of exploitation activity in the next 30 days.

On this page
Win32k Elevation of Privilege Vulnerability

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
82% (unchanged from 82% a week ago; 82% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-17, due 2021-12-01, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-40449 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-40449?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-40449?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-40449 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.2237
Microsoft Windows Server 2019from 10.0.0 before 10.0.17763.2237
Microsoft Windows Server 2019 (Server Core installation)from 10.0.0 before 10.0.17763.2237
Microsoft Windows 10 Version 1909from 10.0.0 before 10.0.18363.1854
Microsoft Windows 10 Version 21H1from 10.0.0 before 10.0.19041.1288
Microsoft Windows Server 2022from 10.0.0 before 10.0.20348.288
Microsoft Windows 10 Version 2004from 10.0.0 before 10.0.19041.1288
Microsoft Windows Server version 2004from 10.0.0 before 10.0.19041.1288
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19041.1288
Microsoft Windows Server version 20H2from 10.0.0 before 10.0.19042.1288
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.258
Microsoft Windows 10 Version 1507from 10.0.0 before 10.0.10240.19086
Microsoft Windows 10 Version 1607from 10.0.0 before 10.0.14393.4704
Microsoft Windows Server 2016from 10.0.0 before 10.0.14393.4704
Microsoft Windows Server 2016 (Server Core installation)from 10.0.0 before 10.0.14393.4704
Microsoft Windows 7from 6.1.0 before 6.1.7601.25740
Microsoft Windows 7 Service Pack 1from 6.1.0 before 6.1.7601.25740
Microsoft Windows 8.1from 6.3.0 before 6.3.9600.20144
Microsoft Windows Server 2008 Service Pack 2from 6.0.0 before 6.0.6003.21251
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.0 before 6.0.6003.21251
Microsoft Windows Server 2008 Service Pack 2from 6.0.0 before 6.0.6003.21251
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.0 before 6.1.7601.25740
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.0.0 before 6.1.7601.25740
Microsoft Windows Server 2012from 6.2.0 before 6.2.9200.23490
Microsoft Windows Server 2012 (Server Core installation)from 6.2.0 before 6.2.9200.23490
Microsoft Windows Server 2012 R2from 6.3.0 before 6.3.9600.20144
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.0 before 6.3.9600.20144

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • Joe1sn/CVE_2021_40449 Harbor Check: matches CVE 1 star, C++, created
    poc and exp for CVE_2021_40449, related to my analyze

References

Check your stackJSON