Protection mechanism failure in Windows Shell allows an unauthorized attacker to perform spoofing over a network.
CVE-2026-32202
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-04-28), indicating real-world exploitation has been confirmed by US federal agencies. the CNA's CVSS baseline 4.3 retained for reference (NVD's own analysis pending). 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
- 4.3
- 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
- 99.1%
- KEV
- ⚠ Exploited
Published
April 14, 2026
Last Modified
June 19, 2026
Advisory Details (2)
Auto-updated May 20, 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-2026-32202Security 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-2026-32202Vendor Advisories for CVE-2026-32202(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 76× in last 7d / 367× 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 725 total refreshes for this CVE.
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:08 UTCEG score recompute
- 2026-07-22 23:57 UTCEG score recompute
- 2026-07-22 23:57 UTCVendor advisory
- 2026-07-22 23:57 UTCGHSA enrichment
- 2026-07-22 19:50 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 15:43 UTCEG score recompute
- 2026-07-22 15:43 UTCVendor advisory
- 2026-07-22 15:43 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 11:36 UTCVendor advisory
- 2026-07-22 11:35 UTCGHSA enrichment
- 2026-07-22 07:28 UTCVendor advisory
- 2026-07-22 07:28 UTCGHSA enrichment
- 2026-07-22 03:21 UTCVendor advisory
- 2026-07-22 03:21 UTCGHSA enrichment
- 2026-07-21 23:15 UTCVendor advisory
- 2026-07-21 23:15 UTCGHSA enrichment
- 2026-07-21 17:48 UTCEG score recompute
- 2026-07-21 17:48 UTCVendor advisory
- 2026-07-21 17:48 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:42 UTCVendor advisory
- 2026-07-21 13:41 UTCGHSA enrichment
- 2026-07-21 09:34 UTCVendor advisory
- 2026-07-21 09:34 UTCGHSA enrichment
- 2026-07-21 05:27 UTCVendor advisory
- 2026-07-21 05:27 UTCGHSA enrichment
- 2026-07-21 01:21 UTCVendor advisory
- 2026-07-21 01:21 UTCGHSA enrichment
- 2026-07-20 21:14 UTCEG score recompute
- 2026-07-20 21:14 UTCVendor advisory
- 2026-07-20 21:14 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCVendor advisory
- 2026-07-20 17:08 UTCGHSA enrichment
- 2026-07-20 13:01 UTCGHSA enrichment
- 2026-07-20 08:55 UTCVendor advisory
- 2026-07-20 08:54 UTCGHSA enrichment
- 2026-07-20 04:48 UTCVendor advisory
- 2026-07-20 04:48 UTCGHSA enrichment
- 2026-07-20 00:41 UTCVendor advisory
- 2026-07-20 00:41 UTCGHSA enrichment
- 2026-07-19 20:35 UTCVendor advisory
- 2026-07-19 20:35 UTCGHSA enrichment
- 2026-07-19 16:29 UTCEG score recompute
- 2026-07-19 16:29 UTCVendor advisory
- 2026-07-19 16:29 UTCGHSA enrichment
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 12:22 UTCVendor advisory
- 2026-07-19 12:22 UTCGHSA enrichment
- 2026-07-19 08:16 UTCVendor advisory
- 2026-07-19 08:16 UTCGHSA enrichment
- 2026-07-19 04:09 UTCVendor advisory
- 2026-07-19 04:09 UTCGHSA enrichment
- 2026-07-19 00:03 UTCGHSA enrichment
- 2026-07-18 19:55 UTCVendor advisory
- 2026-07-18 19:55 UTCGHSA enrichment
- 2026-07-18 15:49 UTCVendor advisory
- 2026-07-18 15:49 UTCGHSA enrichment
- 2026-07-18 11:42 UTCVendor advisory
- 2026-07-18 11:42 UTCGHSA enrichment
- 2026-07-18 07:36 UTCVendor advisory
- 2026-07-18 07:36 UTCGHSA enrichment
- 2026-07-18 03:30 UTCVendor advisory
- 2026-07-18 03:30 UTCGHSA enrichment
- 2026-07-17 23:24 UTCVendor advisory
- 2026-07-17 23:24 UTCGHSA enrichment
- 2026-07-17 19:18 UTCVendor advisory
- 2026-07-17 19:18 UTCGHSA enrichment
- 2026-07-17 15:12 UTCVendor advisory
- 2026-07-17 15:12 UTCGHSA enrichment
- 2026-07-17 11:06 UTCVendor advisory
- 2026-07-17 11:06 UTCGHSA enrichment
- 2026-07-17 06:59 UTCVendor advisory
- 2026-07-17 06:59 UTCGHSA enrichment
- 2026-07-17 02:53 UTCVendor advisory
- 2026-07-17 02:53 UTCGHSA enrichment
- 2026-07-16 22:47 UTCVendor advisory
- 2026-07-16 22:47 UTCGHSA enrichment
- 2026-07-16 18:40 UTCVendor advisory
- 2026-07-16 18:40 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 14:34 UTCVendor advisory
- 2026-07-16 14:34 UTCGHSA enrichment
- 2026-07-16 10:28 UTCVendor advisory
- 2026-07-16 10:28 UTCGHSA enrichment
- 2026-07-16 06:21 UTCVendor advisory
- 2026-07-16 06:21 UTCGHSA enrichment
- 2026-07-16 02:14 UTCGHSA enrichment
Publicly available exploits
(2 references)Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-52601First seen May 29, 2026
Microsoft - NTLMv2 Hash Capture
Open source ↗ - GitHub PoCvirus-or-not/CVE-2026-32202First seen Apr 30, 2026
Windows Shell Spoofing Vulnerability
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS 91%CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS 99%CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8MEDIUM
- CVE-2020-10887EG 9.8EPSS 90%CRITICAL
- CVE-2017-3197EG 9.8EPSS 92%CRITICAL
- CVE-2018-9318EG 9.8EPSS 90%CRITICAL
- CVE-2018-9311EG 9.8EPSS 90%CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2022-22759EG 9.6CRITICAL
Frequently asked(6)
What is CVE-2026-32202?
When was CVE-2026-32202 disclosed?
Is CVE-2026-32202 actively exploited?
What is the CVSS score of CVE-2026-32202?
Which products are affected by CVE-2026-32202?
How do I remediate CVE-2026-32202?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32202
Is Your Infrastructure Affected by CVE-2026-32202?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.