Internet Explorer Memory Corruption Vulnerability
CVE-2021-26411
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 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
- 99.6%
- KEV
- ⚠ Exploited
Published
March 11, 2021
Last Modified
October 30, 2025
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-2021-26411Security 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-26411Weakness Classification(3)
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 66× in last 7d / 372× 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 703 total refreshes for this CVE.
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 01:58 UTCEG score recompute
- 2026-07-22 23:14 UTCVendor advisory
- 2026-07-22 23:14 UTCGHSA enrichment
- 2026-07-22 22:45 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:23 UTCGHSA enrichment
- 2026-07-22 15:34 UTCEG score recompute
- 2026-07-22 15:34 UTCVendor advisory
- 2026-07-22 15:34 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 11:45 UTCVendor advisory
- 2026-07-22 11:45 UTCGHSA enrichment
- 2026-07-22 07:55 UTCVendor advisory
- 2026-07-22 07:55 UTCGHSA enrichment
- 2026-07-22 04:05 UTCVendor advisory
- 2026-07-22 04:05 UTCGHSA enrichment
- 2026-07-22 00:08 UTCVendor advisory
- 2026-07-22 00:08 UTCGHSA enrichment
- 2026-07-21 18:41 UTCEG score recompute
- 2026-07-21 18:41 UTCVendor advisory
- 2026-07-21 18:40 UTCGHSA enrichment
- 2026-07-21 15:22 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 14:50 UTCVendor advisory
- 2026-07-21 14:50 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:01 UTCVendor advisory
- 2026-07-21 11:01 UTCGHSA enrichment
- 2026-07-21 07:11 UTCVendor advisory
- 2026-07-21 07:11 UTCGHSA enrichment
- 2026-07-21 03:22 UTCVendor advisory
- 2026-07-21 03:21 UTCGHSA enrichment
- 2026-07-20 23:32 UTCVendor advisory
- 2026-07-20 23:32 UTCGHSA enrichment
- 2026-07-20 19:42 UTCEG score recompute
- 2026-07-20 19:42 UTCVendor advisory
- 2026-07-20 19:42 UTCGHSA enrichment
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-20 15:53 UTCGHSA enrichment
- 2026-07-20 12:04 UTCGHSA enrichment
- 2026-07-20 08:15 UTCVendor advisory
- 2026-07-20 08:14 UTCGHSA enrichment
- 2026-07-20 04:25 UTCVendor advisory
- 2026-07-20 04:25 UTCGHSA enrichment
- 2026-07-20 00:35 UTCVendor advisory
- 2026-07-20 00:35 UTCGHSA enrichment
- 2026-07-19 20:45 UTCVendor advisory
- 2026-07-19 20:45 UTCGHSA enrichment
- 2026-07-19 16:56 UTCVendor advisory
- 2026-07-19 16:56 UTCGHSA enrichment
- 2026-07-19 13:07 UTCVendor advisory
- 2026-07-19 13:07 UTCGHSA enrichment
- 2026-07-19 09:17 UTCVendor advisory
- 2026-07-19 09:17 UTCGHSA enrichment
- 2026-07-19 05:28 UTCVendor advisory
- 2026-07-19 05:28 UTCGHSA enrichment
- 2026-07-19 01:38 UTCGHSA enrichment
- 2026-07-18 21:48 UTCVendor advisory
- 2026-07-18 21:48 UTCGHSA enrichment
- 2026-07-18 17:59 UTCVendor advisory
- 2026-07-18 17:59 UTCGHSA enrichment
- 2026-07-18 14:10 UTCVendor advisory
- 2026-07-18 14:10 UTCGHSA enrichment
- 2026-07-18 10:21 UTCVendor advisory
- 2026-07-18 10:21 UTCGHSA enrichment
- 2026-07-18 06:31 UTCVendor advisory
- 2026-07-18 06:31 UTCGHSA enrichment
- 2026-07-18 02:42 UTCVendor advisory
- 2026-07-18 02:42 UTCGHSA enrichment
- 2026-07-17 22:53 UTCVendor advisory
- 2026-07-17 22:53 UTCGHSA enrichment
- 2026-07-17 19:04 UTCVendor advisory
- 2026-07-17 19:04 UTCGHSA enrichment
- 2026-07-17 15:14 UTCVendor advisory
- 2026-07-17 15:14 UTCGHSA enrichment
- 2026-07-17 11:25 UTCVendor advisory
- 2026-07-17 11:25 UTCGHSA enrichment
- 2026-07-17 07:35 UTCEG score recompute
- 2026-07-17 07:35 UTCVendor advisory
- 2026-07-17 07:35 UTCGHSA enrichment
- 2026-07-17 03:46 UTCVendor advisory
- 2026-07-17 03:46 UTCGHSA enrichment
- 2026-07-16 23:56 UTCVendor advisory
- 2026-07-16 23:56 UTCGHSA enrichment
- 2026-07-16 20:07 UTCVendor advisory
- 2026-07-16 20:07 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:00 UTCEPSS rescore
- 2026-07-16 16:17 UTCGHSA enrichment
- 2026-07-16 12:27 UTCVendor advisory
- 2026-07-16 12:27 UTCGHSA enrichment
- 2026-07-16 08:38 UTCVendor advisory
- 2026-07-16 08:38 UTCGHSA enrichment
- 2026-07-16 04:48 UTCVendor advisory
- 2026-07-16 04:48 UTCGHSA enrichment
- 2026-07-16 00:59 UTCVendor advisory
- 2026-07-16 00:59 UTCGHSA enrichment
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.
- Open source ↗GitHub PoCCrackerCat/CVE-2021-26411First seen Nov 22, 2021
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-119 · CWE-787
Frequently asked(6)
What is CVE-2021-26411?
When was CVE-2021-26411 disclosed?
Is CVE-2021-26411 actively exploited?
What is the CVSS score of CVE-2021-26411?
Which products are affected by CVE-2021-26411?
How do I remediate CVE-2021-26411?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2021-26411
Is Your Infrastructure Affected by CVE-2021-26411?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.