Protection mechanism failure in Windows Shell allows an unauthorized attacker to bypass a security feature over a network.
CVE-2026-21510
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-02-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.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
- 8.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
- 97.8%
- KEV
- ⚠ Exploited
Published
February 10, 2026
Last Modified
February 11, 2026
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-2026-21510Security 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-21510Weakness 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 94× in last 7d / 402× 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 714 total refreshes for this CVE.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:06 UTCEG score recompute
- 2026-07-22 23:46 UTCEG score recompute
- 2026-07-22 23:46 UTCVendor advisory
- 2026-07-22 23:46 UTCGHSA enrichment
- 2026-07-22 19:42 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 15:41 UTCEG score recompute
- 2026-07-22 15:41 UTCVendor advisory
- 2026-07-22 15:40 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 11:38 UTCVendor advisory
- 2026-07-22 11:38 UTCGHSA enrichment
- 2026-07-22 07:35 UTCVendor advisory
- 2026-07-22 07:35 UTCGHSA enrichment
- 2026-07-22 03:33 UTCVendor advisory
- 2026-07-22 03:33 UTCGHSA enrichment
- 2026-07-21 23:29 UTCVendor advisory
- 2026-07-21 23:29 UTCGHSA enrichment
- 2026-07-21 19:25 UTCEG score recompute
- 2026-07-21 19:25 UTCVendor advisory
- 2026-07-21 19:25 UTCGHSA enrichment
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-21 15:22 UTCVendor advisory
- 2026-07-21 15:22 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:20 UTCVendor advisory
- 2026-07-21 11:20 UTCGHSA enrichment
- 2026-07-21 07:18 UTCVendor advisory
- 2026-07-21 07:17 UTCGHSA enrichment
- 2026-07-21 03:16 UTCVendor advisory
- 2026-07-21 03:16 UTCGHSA enrichment
- 2026-07-20 23:14 UTCVendor advisory
- 2026-07-20 23:14 UTCGHSA enrichment
- 2026-07-20 19:12 UTCEG score recompute
- 2026-07-20 19:12 UTCVendor advisory
- 2026-07-20 19:12 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 15:10 UTCVendor advisory
- 2026-07-20 15:09 UTCGHSA enrichment
- 2026-07-20 11:07 UTCGHSA enrichment
- 2026-07-20 07:05 UTCVendor advisory
- 2026-07-20 07:05 UTCGHSA enrichment
- 2026-07-20 03:03 UTCVendor advisory
- 2026-07-20 03:03 UTCGHSA enrichment
- 2026-07-19 23:00 UTCVendor advisory
- 2026-07-19 23:00 UTCGHSA enrichment
- 2026-07-19 18:58 UTCVendor advisory
- 2026-07-19 18:58 UTCGHSA enrichment
- 2026-07-19 14:56 UTCEG score recompute
- 2026-07-19 14:56 UTCVendor advisory
- 2026-07-19 14:56 UTCGHSA enrichment
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 10:54 UTCVendor advisory
- 2026-07-19 10:54 UTCGHSA enrichment
- 2026-07-19 06:52 UTCVendor advisory
- 2026-07-19 06:52 UTCGHSA enrichment
- 2026-07-19 02:50 UTCEG score recompute
- 2026-07-19 02:50 UTCVendor advisory
- 2026-07-19 02:50 UTCGHSA enrichment
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 22:48 UTCGHSA enrichment
- 2026-07-18 18:46 UTCVendor advisory
- 2026-07-18 18:46 UTCGHSA enrichment
- 2026-07-18 14:44 UTCVendor advisory
- 2026-07-18 14:44 UTCGHSA enrichment
- 2026-07-18 10:42 UTCEG score recompute
- 2026-07-18 10:42 UTCVendor advisory
- 2026-07-18 10:41 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 06:40 UTCVendor advisory
- 2026-07-18 06:40 UTCGHSA enrichment
- 2026-07-18 02:38 UTCVendor advisory
- 2026-07-18 02:38 UTCGHSA enrichment
- 2026-07-17 22:36 UTCVendor advisory
- 2026-07-17 22:36 UTCGHSA enrichment
- 2026-07-17 18:34 UTCVendor advisory
- 2026-07-17 18:34 UTCGHSA enrichment
- 2026-07-17 14:32 UTCVendor advisory
- 2026-07-17 14:32 UTCGHSA enrichment
- 2026-07-17 10:30 UTCEG score recompute
- 2026-07-17 10:30 UTCVendor advisory
- 2026-07-17 10:30 UTCGHSA enrichment
- 2026-07-17 06:28 UTCVendor advisory
- 2026-07-17 06:28 UTCGHSA enrichment
- 2026-07-17 02:26 UTCVendor advisory
- 2026-07-17 02:26 UTCGHSA enrichment
- 2026-07-16 22:24 UTCVendor advisory
- 2026-07-16 22:24 UTCGHSA enrichment
- 2026-07-16 18:22 UTCVendor advisory
- 2026-07-16 18:21 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:18 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCEpSiLoNPoInTOrI/EpSiLoNPoInTlnkFirst seen May 9, 2026
CVE-2026-21510 LNK generator PoC
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-21510?
When was CVE-2026-21510 disclosed?
Is CVE-2026-21510 actively exploited?
What is the CVSS score of CVE-2026-21510?
Which products are affected by CVE-2026-21510?
How do I remediate CVE-2026-21510?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-21510
Is Your Infrastructure Affected by CVE-2026-21510?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.