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 PROB
- 26%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
February 10, 2026
Last Modified
August 19, 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 99× in last 7d / 409× 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,473 total refreshes for this CVE.
- 2026-09-19 20:28 UTCVendor advisory
- 2026-09-19 20:28 UTCGHSA enrichment
- 2026-09-19 16:26 UTCEG score recompute
- 2026-09-19 16:26 UTCVendor advisory
- 2026-09-19 16:26 UTCGHSA enrichment
- 2026-09-19 12:24 UTCVendor advisory
- 2026-09-19 12:24 UTCGHSA enrichment
- 2026-09-19 08:22 UTCVendor advisory
- 2026-09-19 08:22 UTCGHSA enrichment
- 2026-09-19 04:20 UTCVendor advisory
- 2026-09-19 04:20 UTCGHSA enrichment
- 2026-09-19 00:18 UTCVendor advisory
- 2026-09-19 00:18 UTCGHSA enrichment
- 2026-09-18 20:16 UTCEG score recompute
- 2026-09-18 20:16 UTCVendor advisory
- 2026-09-18 20:16 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 16:13 UTCVendor advisory
- 2026-09-18 16:12 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 12:10 UTCVendor advisory
- 2026-09-18 12:10 UTCGHSA enrichment
- 2026-09-18 08:09 UTCVendor advisory
- 2026-09-18 08:09 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-18 04:07 UTCVendor advisory
- 2026-09-18 04:07 UTCGHSA enrichment
- 2026-09-18 00:05 UTCVendor advisory
- 2026-09-18 00:05 UTCGHSA enrichment
- 2026-09-17 20:03 UTCEG score recompute
- 2026-09-17 20:03 UTCVendor advisory
- 2026-09-17 20:03 UTCGHSA enrichment
- 2026-09-17 16:01 UTCVendor advisory
- 2026-09-17 16:01 UTCGHSA enrichment
- 2026-09-17 11:59 UTCVendor advisory
- 2026-09-17 11:59 UTCGHSA enrichment
- 2026-09-17 07:57 UTCVendor advisory
- 2026-09-17 07:57 UTCGHSA enrichment
- 2026-09-17 03:55 UTCVendor advisory
- 2026-09-17 03:55 UTCGHSA enrichment
- 2026-09-16 23:53 UTCVendor advisory
- 2026-09-16 23:53 UTCGHSA enrichment
- 2026-09-16 19:51 UTCVendor advisory
- 2026-09-16 19:51 UTCGHSA enrichment
- 2026-09-16 15:49 UTCEG score recompute
- 2026-09-16 15:49 UTCVendor advisory
- 2026-09-16 15:49 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 11:47 UTCVendor advisory
- 2026-09-16 11:47 UTCGHSA enrichment
- 2026-09-16 07:45 UTCEG score recompute
- 2026-09-16 07:45 UTCVendor advisory
- 2026-09-16 07:45 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 03:42 UTCVendor advisory
- 2026-09-16 03:42 UTCGHSA enrichment
- 2026-09-15 23:40 UTCVendor advisory
- 2026-09-15 23:40 UTCGHSA enrichment
- 2026-09-15 19:38 UTCVendor advisory
- 2026-09-15 19:38 UTCGHSA enrichment
- 2026-09-15 15:36 UTCVendor advisory
- 2026-09-15 15:36 UTCGHSA enrichment
- 2026-09-15 11:34 UTCVendor advisory
- 2026-09-15 11:34 UTCGHSA enrichment
- 2026-09-15 07:31 UTCVendor advisory
- 2026-09-15 07:31 UTCGHSA enrichment
- 2026-09-15 03:29 UTCEG score recompute
- 2026-09-15 03:29 UTCVendor advisory
- 2026-09-15 03:29 UTCGHSA enrichment
- 2026-09-14 23:27 UTCVendor advisory
- 2026-09-14 23:27 UTCGHSA enrichment
- 2026-09-14 19:25 UTCVendor advisory
- 2026-09-14 19:25 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 15:23 UTCVendor advisory
- 2026-09-14 15:23 UTCGHSA enrichment
- 2026-09-14 11:21 UTCVendor advisory
- 2026-09-14 11:21 UTCGHSA enrichment
- 2026-09-14 07:20 UTCVendor advisory
- 2026-09-14 07:20 UTCGHSA enrichment
- 2026-09-14 03:18 UTCVendor advisory
- 2026-09-14 03:18 UTCGHSA enrichment
- 2026-09-13 23:16 UTCVendor advisory
- 2026-09-13 23:16 UTCGHSA enrichment
- 2026-09-13 19:14 UTCEG score recompute
- 2026-09-13 19:14 UTCVendor advisory
- 2026-09-13 19:14 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 15:12 UTCVendor advisory
- 2026-09-13 15:12 UTCGHSA enrichment
- 2026-09-13 11:10 UTCVendor advisory
- 2026-09-13 11:10 UTCGHSA enrichment
- 2026-09-13 07:07 UTCVendor advisory
- 2026-09-13 07:07 UTCGHSA enrichment
- 2026-09-13 03:06 UTCVendor advisory
- 2026-09-13 03:06 UTCGHSA enrichment
- 2026-09-12 23:04 UTCVendor advisory
- 2026-09-12 23:04 UTCGHSA enrichment
- 2026-09-12 19:02 UTCEG score recompute
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 PoCEpSiLoNPoInTOrI/EpSiLoNPoInTlnkFirst seen May 9, 2026
CVE-2026-21510 LNK generator PoC
Open source ↗ - GitHub PoCandreassudo/CVE-2026-21510-CVSS-8.8-Important-Windows-Shell-security-feature-bypassFirst seen Feb 11, 2026
CVE-2026-21510 (CVSS 8.8, Important) — Windows Shell security feature bypass. An attacker can trick a user into clicking a malicious link or shortcut file to bypass SmartScreen/Shell warnings and execute code without prompts. Publicly disclosed and exploited.
Open source ↗
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.