Windows NTFS Elevation of Privilege Vulnerability
CVE-2021-31956
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. 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
- 7.8
- 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
- 22%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
June 8, 2021
Last Modified
January 13, 2026
Advisory Details (2)
Auto-updated Jun 3, 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-31956Security 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-31956Weakness Classification(2)
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 97× in last 7d / 401× 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 1,403 total refreshes for this CVE.
- 2026-09-19 08:49 UTCVendor advisory
- 2026-09-19 08:49 UTCGHSA enrichment
- 2026-09-19 04:35 UTCVendor advisory
- 2026-09-19 04:35 UTCGHSA enrichment
- 2026-09-19 00:22 UTCVendor advisory
- 2026-09-19 00:22 UTCGHSA enrichment
- 2026-09-18 20:10 UTCEG score recompute
- 2026-09-18 20:10 UTCVendor advisory
- 2026-09-18 20:10 UTCGHSA enrichment
- 2026-09-18 19:23 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 15:56 UTCVendor advisory
- 2026-09-18 15:56 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 11:40 UTCVendor advisory
- 2026-09-18 11:40 UTCGHSA enrichment
- 2026-09-18 07:27 UTCVendor advisory
- 2026-09-18 07:27 UTCGHSA enrichment
- 2026-09-18 03:14 UTCVendor advisory
- 2026-09-18 03:14 UTCGHSA enrichment
- 2026-09-17 23:01 UTCEG score recompute
- 2026-09-17 23:01 UTCVendor advisory
- 2026-09-17 23:01 UTCGHSA enrichment
- 2026-09-17 19:23 UTCEPSS rescore
- 2026-09-17 19:23 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-17 18:47 UTCVendor advisory
- 2026-09-17 18:46 UTCGHSA enrichment
- 2026-09-17 14:30 UTCVendor advisory
- 2026-09-17 14:30 UTCGHSA enrichment
- 2026-09-17 10:17 UTCVendor advisory
- 2026-09-17 10:17 UTCGHSA enrichment
- 2026-09-17 06:04 UTCVendor advisory
- 2026-09-17 06:04 UTCGHSA enrichment
- 2026-09-17 01:51 UTCVendor advisory
- 2026-09-17 01:51 UTCGHSA enrichment
- 2026-09-16 21:37 UTCVendor advisory
- 2026-09-16 21:37 UTCGHSA enrichment
- 2026-09-16 17:24 UTCEG score recompute
- 2026-09-16 17:24 UTCVendor advisory
- 2026-09-16 17:24 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-16 13:07 UTCVendor advisory
- 2026-09-16 13:07 UTCGHSA enrichment
- 2026-09-16 08:54 UTCEG score recompute
- 2026-09-16 08:54 UTCVendor advisory
- 2026-09-16 08:54 UTCGHSA enrichment
- 2026-09-16 04:41 UTCVendor advisory
- 2026-09-16 04:41 UTCGHSA enrichment
- 2026-09-16 00:28 UTCVendor advisory
- 2026-09-16 00:28 UTCGHSA enrichment
- 2026-09-15 20:14 UTCVendor advisory
- 2026-09-15 20:14 UTCGHSA enrichment
- 2026-09-15 16:01 UTCVendor advisory
- 2026-09-15 16:01 UTCGHSA enrichment
- 2026-09-15 11:47 UTCVendor advisory
- 2026-09-15 11:47 UTCGHSA enrichment
- 2026-09-15 07:34 UTCVendor advisory
- 2026-09-15 07:34 UTCGHSA enrichment
- 2026-09-15 03:20 UTCEG score recompute
- 2026-09-15 03:20 UTCVendor advisory
- 2026-09-15 03:20 UTCGHSA enrichment
- 2026-09-15 03:06 UTCEPSS rescore
- 2026-09-14 23:07 UTCVendor advisory
- 2026-09-14 23:07 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 18:54 UTCVendor advisory
- 2026-09-14 18:54 UTCGHSA enrichment
- 2026-09-14 14:41 UTCVendor advisory
- 2026-09-14 14:41 UTCGHSA enrichment
- 2026-09-14 10:28 UTCVendor advisory
- 2026-09-14 10:28 UTCGHSA enrichment
- 2026-09-14 06:15 UTCVendor advisory
- 2026-09-14 06:15 UTCGHSA enrichment
- 2026-09-14 02:02 UTCVendor advisory
- 2026-09-14 02:02 UTCGHSA enrichment
- 2026-09-13 21:49 UTCVendor advisory
- 2026-09-13 21:49 UTCGHSA enrichment
- 2026-09-13 17:36 UTCVendor advisory
- 2026-09-13 17:36 UTCGHSA enrichment
- 2026-09-13 13:23 UTCVendor advisory
- 2026-09-13 13:23 UTCGHSA enrichment
- 2026-09-13 09:10 UTCVendor advisory
- 2026-09-13 09:10 UTCGHSA enrichment
- 2026-09-13 04:58 UTCVendor advisory
- 2026-09-13 04:57 UTCGHSA enrichment
- 2026-09-13 00:45 UTCVendor advisory
- 2026-09-13 00:45 UTCGHSA enrichment
- 2026-09-12 20:32 UTCVendor advisory
- 2026-09-12 20:32 UTCGHSA enrichment
- 2026-09-12 16:19 UTCEG score recompute
- 2026-09-12 16:19 UTCVendor advisory
- 2026-09-12 16:19 UTCGHSA enrichment
- 2026-09-12 14:57 UTCEPSS rescore
- 2026-09-12 12:06 UTCVendor advisory
- 2026-09-12 12:06 UTCGHSA enrichment
- 2026-09-12 07:52 UTCVendor advisory
- 2026-09-12 07:52 UTCGHSA enrichment
- 2026-09-12 03:40 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoChoangprod/CVE-2021-31956-POCFirst seen Jun 5, 2023
- GitHub PoCY3A/CVE-2021-31956First seen Sep 2, 2022
Win10 20H2 LPE for CVE-2021-31956
Open source ↗ - Open source ↗GitHub PoCaazhuliang/CVE-2021-31956-EXPFirst seen Jan 11, 2022
Frequently asked(6)
What is CVE-2021-31956?
When was CVE-2021-31956 disclosed?
Is CVE-2021-31956 actively exploited?
What is the CVSS score of CVE-2021-31956?
Which products are affected by CVE-2021-31956?
How do I remediate CVE-2021-31956?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-31956
Is Your Infrastructure Affected by CVE-2021-31956?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.