Windows Runtime Remote Code Execution Vulnerability
CVE-2022-21971
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-08-18), 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
- 54%
- EPSS %ILE
- 99%
- KEV
- ⚠ Exploited
Published
February 9, 2022
Last Modified
October 30, 2025
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-2022-21971Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21971Weakness 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 88× in last 7d / 371× 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,219 total refreshes for this CVE.
- 2026-09-08 10:11 UTCVendor advisory
- 2026-09-08 10:10 UTCGHSA enrichment
- 2026-09-08 05:51 UTCVendor advisory
- 2026-09-08 05:51 UTCGHSA enrichment
- 2026-09-08 01:31 UTCVendor advisory
- 2026-09-08 01:31 UTCGHSA enrichment
- 2026-09-07 21:13 UTCVendor advisory
- 2026-09-07 21:13 UTCGHSA enrichment
- 2026-09-07 16:55 UTCVendor advisory
- 2026-09-07 16:55 UTCGHSA enrichment
- 2026-09-07 12:37 UTCVendor advisory
- 2026-09-07 12:36 UTCGHSA enrichment
- 2026-09-07 08:17 UTCVendor advisory
- 2026-09-07 08:16 UTCGHSA enrichment
- 2026-09-07 03:58 UTCVendor advisory
- 2026-09-07 03:58 UTCGHSA enrichment
- 2026-09-06 23:41 UTCVendor advisory
- 2026-09-06 23:41 UTCGHSA enrichment
- 2026-09-06 19:22 UTCVendor advisory
- 2026-09-06 19:22 UTCGHSA enrichment
- 2026-09-06 15:02 UTCEG score recompute
- 2026-09-06 15:02 UTCVendor advisory
- 2026-09-06 15:02 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 10:42 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-06 10:42 UTCGHSA enrichment
- 2026-09-06 06:24 UTCVendor advisory
- 2026-09-06 06:24 UTCGHSA enrichment
- 2026-09-06 02:06 UTCVendor advisory
- 2026-09-06 02:06 UTCGHSA enrichment
- 2026-09-05 21:47 UTCVendor advisory
- 2026-09-05 21:47 UTCGHSA enrichment
- 2026-09-05 17:28 UTCEG score recompute
- 2026-09-05 17:28 UTCVendor advisory
- 2026-09-05 17:28 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 13:10 UTCVendor advisory
- 2026-09-05 13:10 UTCGHSA enrichment
- 2026-09-05 08:52 UTCVendor advisory
- 2026-09-05 08:52 UTCGHSA enrichment
- 2026-09-05 04:34 UTCVendor advisory
- 2026-09-05 04:34 UTCGHSA enrichment
- 2026-09-05 00:15 UTCVendor advisory
- 2026-09-05 00:15 UTCGHSA enrichment
- 2026-09-04 19:57 UTCVendor advisory
- 2026-09-04 19:56 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 15:37 UTCEG score recompute
- 2026-09-04 15:37 UTCVendor advisory
- 2026-09-04 15:37 UTCGHSA enrichment
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 11:20 UTCVendor advisory
- 2026-09-04 11:20 UTCGHSA enrichment
- 2026-09-04 07:02 UTCVendor advisory
- 2026-09-04 07:01 UTCGHSA enrichment
- 2026-09-04 02:39 UTCVendor advisory
- 2026-09-04 02:39 UTCGHSA enrichment
- 2026-09-03 22:18 UTCVendor advisory
- 2026-09-03 22:18 UTCGHSA enrichment
- 2026-09-03 18:00 UTCVendor advisory
- 2026-09-03 17:59 UTCGHSA enrichment
- 2026-09-03 13:39 UTCVendor advisory
- 2026-09-03 13:39 UTCGHSA enrichment
- 2026-09-03 09:19 UTCVendor advisory
- 2026-09-03 09:19 UTCGHSA enrichment
- 2026-09-03 05:02 UTCVendor advisory
- 2026-09-03 05:01 UTCGHSA enrichment
- 2026-09-03 00:41 UTCVendor advisory
- 2026-09-03 00:41 UTCGHSA enrichment
- 2026-09-02 20:22 UTCVendor advisory
- 2026-09-02 20:22 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 16:03 UTCEG score recompute
- 2026-09-02 16:03 UTCVendor advisory
- 2026-09-02 16:03 UTCGHSA enrichment
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 11:42 UTCVendor advisory
- 2026-09-02 11:42 UTCGHSA enrichment
- 2026-09-02 07:24 UTCVendor advisory
- 2026-09-02 07:24 UTCGHSA enrichment
- 2026-09-02 03:06 UTCVendor advisory
- 2026-09-02 03:06 UTCGHSA enrichment
- 2026-09-01 22:47 UTCVendor advisory
- 2026-09-01 22:47 UTCGHSA enrichment
- 2026-09-01 18:29 UTCVendor advisory
- 2026-09-01 18:28 UTCGHSA enrichment
- 2026-09-01 14:08 UTCVendor advisory
- 2026-09-01 14:08 UTCGHSA enrichment
- 2026-09-01 09:50 UTCVendor advisory
- 2026-09-01 09:50 UTCGHSA enrichment
- 2026-09-01 05:32 UTCEG score recompute
- 2026-09-01 05:32 UTCVendor advisory
- 2026-09-01 05:31 UTCGHSA enrichment
- 2026-09-01 01:11 UTCVendor advisory
- 2026-09-01 01:11 UTCGHSA enrichment
- 2026-08-31 20:51 UTCVendor advisory
- 2026-08-31 20:51 UTCGHSA enrichment
- 2026-08-31 16:33 UTCVendor advisory
- 2026-08-31 16:33 UTCGHSA enrichment
- 2026-08-31 14:19 UTCCISA KEV update
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.
- GitHub PoCMalwareman007/CVE-2022-21971First seen Oct 7, 2022
POC Of CVE-2022-21971
Open source ↗ - Open source ↗GitHub PoCtufanturhan/CVE-2022-21971-Windows-Runtime-RCEFirst seen Apr 15, 2022
- GitHub PoC0vercl0k/CVE-2022-21971First seen Feb 26, 2022
PoC for CVE-2022-21971 "Windows Runtime Remote Code Execution Vulnerability"
Open source ↗
Frequently asked(6)
What is CVE-2022-21971?
When was CVE-2022-21971 disclosed?
Is CVE-2022-21971 actively exploited?
What is the CVSS score of CVE-2022-21971?
Which products are affected by CVE-2022-21971?
How do I remediate CVE-2022-21971?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-21971
Is Your Infrastructure Affected by CVE-2022-21971?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.