CVE-2021-26411

Internet Explorer Memory Corruption Vulnerability

HIGH
8.8
CVSS Score
Published: March 11, 2021 at 03:07 PM UTC
Updated: October 1, 2026 at 09:17 PM UTC
17 products affected across 1 vendorInternet ExplorerEdgeWindows Server 2016

Using Internet Explorer 9 by Microsoft?

Get instant alerts when new vulnerabilities affect Internet Explorer 9 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploitation
CISA KEV
Exploit prediction
EPSS 82%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score81.7%

EPSS (Exploit Prediction Scoring System) estimates a 81.7% chance this CVE is exploited in the wild within the next 30 days — higher than 100% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Internet Explorer contains an unspecified vulnerability that allows for memory corruption.

Required Action
Apply updates per vendor instructions.
Ransomware Use
Known
Added to KEV
Nov 3, 2021
Remediation Due
Nov 17, 2021
1810 days overdue

Description

Internet Explorer Memory Corruption Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0..0 ≤ v < 10.0.17134.20871.0..0
Affected range stops below 10.0.17134.2087, so it looks safe — our inference, not a vendor statement
microsoft-windows-10-1507 (environment) · microsoft-windows-10-1607 (environment) · microsoft-windows-10-1803 (environment) · microsoft-windows-10-1809 (environment) · microsoft-windows-10-1903 (environment) · microsoft-windows-10-1909 (environment) · microsoft-windows-10-2004 (environment) · microsoft-windows-10-20h2 (environment) · microsoft-windows-server-2016 (environment) · microsoft-windows-server-2019 (environment)
1.0.0 ≤ v < 10.0.17134.20871.0.0 ≤ v < 6.0.6003.210701.0.0119
Affected range stops below 10.0.17134.2087, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.0.6003.21070, so it looks safe — our inference, not a vendor statement
microsoft-windows-10-1507 (environment) · microsoft-windows-10-1607 (environment) · microsoft-windows-10-1803 (environment) · microsoft-windows-10-1809 (environment) · microsoft-windows-10-1903 (environment) · microsoft-windows-10-1909 (environment) · microsoft-windows-10-2004 (environment) · microsoft-windows-10-20h2 (environment) · microsoft-windows-7 (environment) · microsoft-windows-8-1 (environment) · microsoft-windows-rt-8-1 (environment) · microsoft-windows-server-2008 (environment) · microsoft-windows-server-2012 (environment) · microsoft-windows-server-2016 (environment) · microsoft-windows-server-2019 (environment)
All versions
All versions
All versions
All versions
All versions
All versions
All versions
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card