CVE-2021-1732

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2021-7196 (ENISA EUVD) · GHSA-gvwr-5hrc-2gr5 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 78%CVSS: 7.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Windows Win32k Elevation of Privilege Vulnerability

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
78%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
78% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2021-1732

Published

February 25, 2021

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Oct 26, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: microsoft, cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-1732
Microsoft

Security Update Guide - Microsoft Security Response Center

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-1732

Vendor Advisories for CVE-2021-1732(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 179× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,901 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,801 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 02:10 UTCEG score recompute
  2. 2026-11-02 02:10 UTCVendor advisory
  3. 2026-11-02 02:10 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-11-01 01:08 UTCEG score recompute
  5. 2026-11-01 01:08 UTCVendor advisory
  6. 2026-11-01 01:08 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-31 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  8. 2026-10-31 00:03 UTCEG score recompute
  9. 2026-10-31 00:03 UTCVendor advisory
  10. 2026-10-31 00:03 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-29 23:02 UTCEG score recompute
  12. 2026-10-29 23:02 UTCVendor advisory
  13. 2026-10-29 23:02 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-29 16:29 UTCEPSS rescoreEPSS 78% · 99th percentile
  15. 2026-10-28 22:01 UTCEG score recompute
  16. 2026-10-28 22:01 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-27 21:00 UTCEG score recompute
  18. 2026-10-27 21:00 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-27 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  20. 2026-10-26 19:59 UTCEG score recompute
  21. 2026-10-26 19:59 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-26 16:27 UTCEPSS rescoreEPSS 78% · 99th percentile
  23. 2026-10-25 18:58 UTCVendor advisory
  24. 2026-10-25 18:58 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-25 18:36 UTCEG score recompute
Show 75 more
  1. 2026-10-25 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  2. 2026-10-24 17:56 UTCEG score recompute
  3. 2026-10-24 17:56 UTCVendor advisory
  4. 2026-10-24 17:56 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-24 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  6. 2026-10-23 16:55 UTCEG score recompute
  7. 2026-10-23 16:55 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-22 16:29 UTCEPSS rescoreEPSS 78% · 99th percentile
  9. 2026-10-22 15:53 UTCEG score recompute
  10. 2026-10-22 15:53 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-21 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  12. 2026-10-21 14:50 UTCEG score recompute
  13. 2026-10-21 14:50 UTCVendor advisory
  14. 2026-10-21 14:50 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-20 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  16. 2026-10-20 13:50 UTCEG score recompute
  17. 2026-10-20 13:49 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-19 12:48 UTCEG score recompute
  19. 2026-10-19 12:48 UTCVendor advisory
  20. 2026-10-19 12:48 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-18 11:47 UTCVendor advisory
  22. 2026-10-18 11:46 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-18 09:13 UTCEG score recompute
  24. 2026-10-17 10:44 UTCEG score recompute
  25. 2026-10-17 10:44 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-10-16 16:33 UTCEPSS rescoreEPSS 78% · 99th percentile
  27. 2026-10-16 09:43 UTCEG score recompute
  28. 2026-10-16 09:43 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-10-15 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  30. 2026-10-15 08:40 UTCEG score recompute
  31. 2026-10-15 08:40 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-10-14 16:28 UTCEPSS rescoreEPSS 78% · 99th percentile
  33. 2026-10-14 07:37 UTCEG score recompute
  34. 2026-10-14 07:37 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-13 06:35 UTCVendor advisory
  36. 2026-10-13 06:35 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-10-12 19:27 UTCEG score recompute
  38. 2026-10-12 05:33 UTCVendor advisory
  39. 2026-10-12 05:33 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-10-12 01:46 UTCVendor advisory
  41. 2026-10-12 01:46 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-11 22:03 UTCEG score recompute
  43. 2026-10-11 22:03 UTCVendor advisory
  44. 2026-10-11 22:03 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-10-11 18:20 UTCEG score recompute
  46. 2026-10-11 18:20 UTCVendor advisory
  47. 2026-10-11 18:19 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-11 14:37 UTCEG score recompute
  49. 2026-10-11 14:37 UTCVendor advisory
  50. 2026-10-11 14:37 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-10-11 13:43 UTCEPSS rescoreEPSS 78% · 99th percentile
  52. 2026-10-11 10:53 UTCVendor advisory
  53. 2026-10-11 10:53 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-10-11 07:10 UTCVendor advisory
  55. 2026-10-11 07:10 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-10-11 03:27 UTCVendor advisory
  57. 2026-10-11 03:27 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-10-10 23:42 UTCVendor advisory
  59. 2026-10-10 23:41 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-10-10 19:57 UTCVendor advisory
  61. 2026-10-10 19:57 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-10-10 16:14 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-10 12:29 UTCVendor advisory
  64. 2026-10-10 12:29 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-10-10 08:46 UTCVendor advisory
  66. 2026-10-10 08:46 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-10-10 05:03 UTCVendor advisory
  68. 2026-10-10 05:03 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-10-10 01:20 UTCVendor advisory
  70. 2026-10-10 01:20 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-10-09 21:37 UTCVendor advisory
  72. 2026-10-09 21:37 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-10-09 17:55 UTCVendor advisory
  74. 2026-10-09 17:54 UTCGHSA enrichmentGHSA-gvwr-5hrc-2gr5 · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-10-09 14:11 UTCVendor advisory

Publicly available exploits

(8 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 7 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Metasploitexploit/windows/local/cve_2022_21882_win32k✓ verified
    Published Feb 25, 2022

    Win32k ConsoleControl Offset Confusion

    Open source ↗
  • GitHub PoC4dp/CVE-2021-1732
    Published Mar 9, 2023

    CVE-­2021­-1732 Microsoft Windows 10 本地提权漏 研究及Poc/Exploit开发

    Open source ↗
  • GitHub PoCfenalik/CVE-2021-1732
    Published Nov 1, 2022

    CVE-­2021­-1732 Microsoft Windows 10 本地提权漏 研究及Poc/Exploit开发

    Open source ↗
  • GitHub PoCexploitblizzard/Windows-Privilege-Escalation-CVE-2021-1732
    Published Apr 25, 2021

    Read my blog for more info -

    Open source ↗
  • GitHub PoCPai-Po/CVE-2021-1732
    Published Apr 23, 2021

    CVE-2021-1732 poc & exp; tested on 20H2

    Open source ↗
  • GitHub PoCpo4sec/CVE-2021-1732
    Published Apr 23, 2021

    CVE-2021-1732 poc & exp; tested on 20H2

    Open source ↗
  • GitHub PoClinuxdy/CVE-2021-1732_exp
    Published Apr 2, 2021
    Open source ↗
  • GitHub PoCKaLendsi/CVE-2021-1732-Exploit
    Published Mar 5, 2021

    CVE-2021-1732 Exploit

    Open source ↗

Frequently asked(6)

What is CVE-2021-1732?
CVE-2021-1732 is a critical-severity vulnerability; its CVE record was published on February 25, 2021. Windows Win32k Elevation of Privilege Vulnerability
When was CVE-2021-1732 made public?
CVE-2021-1732 was made public on February 9, 2021: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on February 25, 2021. EchelonGraph's copy of the record carries a last-modified date of August 12, 2026; the record at its source may have been updated since.
Is CVE-2021-1732 actively exploited?
Yes. CISA added CVE-2021-1732 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Win32k. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2021-1732?
CVE-2021-1732 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2021-1732?
CVE-2021-1732 affects Microsoft Win32k.
How do I remediate CVE-2021-1732?
A fix for CVE-2021-1732 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-1732 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-1732

Explore →

Is Your Infrastructure Affected by CVE-2021-1732?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.