Microsoft DWM Core Library Elevation of Privilege Vulnerability
CVE-2021-33739
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 8.4 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 7%
- EPSS %ILE
- 93%
- KEV
- ⚠ Exploited
Published
June 8, 2021
Last Modified
October 30, 2025
Advisory Details (2)
Auto-updated Jun 2, 2026Known 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-33739Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-33739Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 67× in last 7d / 393× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 808 total refreshes for this CVE.
- 2026-07-29 11:10 UTCVendor advisory
- 2026-07-29 11:10 UTCGHSA enrichment
- 2026-07-29 07:20 UTCVendor advisory
- 2026-07-29 07:20 UTCGHSA enrichment
- 2026-07-29 03:29 UTCVendor advisory
- 2026-07-29 03:29 UTCGHSA enrichment
- 2026-07-28 23:38 UTCVendor advisory
- 2026-07-28 23:38 UTCGHSA enrichment
- 2026-07-28 19:48 UTCVendor advisory
- 2026-07-28 19:48 UTCGHSA enrichment
- 2026-07-28 15:57 UTCEG score recompute
- 2026-07-28 15:57 UTCVendor advisory
- 2026-07-28 15:57 UTCGHSA enrichment
- 2026-07-28 15:33 UTCEPSS rescore
- 2026-07-28 12:06 UTCVendor advisory
- 2026-07-28 12:06 UTCGHSA enrichment
- 2026-07-28 08:15 UTCVendor advisory
- 2026-07-28 08:15 UTCGHSA enrichment
- 2026-07-28 04:24 UTCVendor advisory
- 2026-07-28 04:23 UTCGHSA enrichment
- 2026-07-28 00:33 UTCVendor advisory
- 2026-07-28 00:33 UTCGHSA enrichment
- 2026-07-27 20:43 UTCVendor advisory
- 2026-07-27 20:43 UTCGHSA enrichment
- 2026-07-27 19:24 UTCCISA KEV update
Show 75 moreShow fewer
- 2026-07-27 17:17 UTCCISA KEV update
- 2026-07-27 16:52 UTCVendor advisory
- 2026-07-27 16:52 UTCGHSA enrichment
- 2026-07-27 13:03 UTCVendor advisory
- 2026-07-27 13:02 UTCGHSA enrichment
- 2026-07-27 09:12 UTCVendor advisory
- 2026-07-27 09:12 UTCGHSA enrichment
- 2026-07-27 05:22 UTCVendor advisory
- 2026-07-27 05:22 UTCGHSA enrichment
- 2026-07-27 01:23 UTCVendor advisory
- 2026-07-27 01:22 UTCGHSA enrichment
- 2026-07-26 21:31 UTCVendor advisory
- 2026-07-26 21:31 UTCGHSA enrichment
- 2026-07-26 17:40 UTCEG score recompute
- 2026-07-26 17:40 UTCVendor advisory
- 2026-07-26 17:39 UTCGHSA enrichment
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-26 13:49 UTCEG score recompute
- 2026-07-26 13:49 UTCVendor advisory
- 2026-07-26 13:49 UTCGHSA enrichment
- 2026-07-26 09:59 UTCVendor advisory
- 2026-07-26 09:59 UTCGHSA enrichment
- 2026-07-26 06:09 UTCVendor advisory
- 2026-07-26 06:09 UTCGHSA enrichment
- 2026-07-26 02:09 UTCEG score recompute
- 2026-07-26 02:09 UTCVendor advisory
- 2026-07-26 02:09 UTCGHSA enrichment
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:01 UTCEG score recompute
- 2026-07-23 00:07 UTCEG score recompute
- 2026-07-23 00:07 UTCVendor advisory
- 2026-07-23 00:06 UTCGHSA enrichment
- 2026-07-22 22:48 UTCEG score recompute
- 2026-07-22 20:15 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:25 UTCEG score recompute
- 2026-07-22 16:25 UTCVendor advisory
- 2026-07-22 16:24 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 12:33 UTCVendor advisory
- 2026-07-22 12:33 UTCGHSA enrichment
- 2026-07-22 08:43 UTCVendor advisory
- 2026-07-22 08:43 UTCGHSA enrichment
- 2026-07-22 04:53 UTCVendor advisory
- 2026-07-22 04:53 UTCGHSA enrichment
- 2026-07-22 01:02 UTCVendor advisory
- 2026-07-22 01:02 UTCGHSA enrichment
- 2026-07-21 21:13 UTCVendor advisory
- 2026-07-21 21:12 UTCGHSA enrichment
- 2026-07-21 17:22 UTCEG score recompute
- 2026-07-21 17:22 UTCVendor advisory
- 2026-07-21 17:22 UTCGHSA enrichment
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:31 UTCVendor advisory
- 2026-07-21 13:31 UTCGHSA enrichment
- 2026-07-21 09:39 UTCVendor advisory
- 2026-07-21 09:39 UTCGHSA enrichment
- 2026-07-21 05:49 UTCVendor advisory
- 2026-07-21 05:49 UTCGHSA enrichment
- 2026-07-21 01:59 UTCVendor advisory
- 2026-07-21 01:59 UTCGHSA enrichment
- 2026-07-20 22:09 UTCVendor advisory
- 2026-07-20 22:09 UTCGHSA enrichment
- 2026-07-20 18:19 UTCEG score recompute
- 2026-07-20 18:19 UTCVendor advisory
- 2026-07-20 18:19 UTCGHSA enrichment
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-20 14:28 UTCGHSA enrichment
Publicly available exploits
(2 references)Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCgiwon9977/CVE-2021-33739_PoC_AnalysisFirst seen Sep 24, 2021
CVE-2021-33739 PoC Analysis
Open source ↗ - Open source ↗GitHub PoCfreeide2017/CVE-2021-33739-POCFirst seen Jun 9, 2021
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-269
Frequently asked(6)
What is CVE-2021-33739?
When was CVE-2021-33739 disclosed?
Is CVE-2021-33739 actively exploited?
What is the CVSS score of CVE-2021-33739?
Which products are affected by CVE-2021-33739?
How do I remediate CVE-2021-33739?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-33739
Is Your Infrastructure Affected by CVE-2021-33739?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.