CVE-2021-40444

Microsoft MSHTML Remote Code Execution Vulnerability

HIGH
8.8
CVSS Score
Published: September 15, 2021 at 11:24 AM UTC
Updated: August 10, 2026 at 08:38 PM UTC
17 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

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

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score97.8%

EPSS (Exploit Prediction Scoring System) estimates a 97.8% 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 MSHTML contains a unspecified vulnerability that allows for remote code execution.

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

Description

<p>Microsoft is investigating reports of a remote code execution vulnerability in MSHTML that affects Microsoft Windows. Microsoft is aware of targeted attacks that attempt to exploit this vulnerability by using specially-crafted Microsoft Office documents.</p> <p>An attacker could craft a malicious ActiveX control to be used by a Microsoft Office document that hosts the browser rendering engine. The attacker would then have to convince the user to open the malicious document. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.</p> <p>Microsoft Defender Antivirus and Microsoft Defender for Endpoint both provide detection and protections for the known vulnerability. Customers should keep antimalware products up to date. Customers who utilize automatic updates do not need to take additional action. Enterprise customers who manage updates should select the detection build 1.349.22.0 or newer and deploy it across their environments. Microsoft Defender for Endpoint alerts will be displayed as: “Suspicious Cpl File Execution”.</p> <p>Upon completion of this investigation, Microsoft will take the appropriate action to help protect our customers. This may include providing a security update through our monthly release process or providing an out-of-cycle security update, depending on customer needs.</p> <p>Please see the <strong>Mitigations</strong> and <strong>Workaround</strong> sections for important information about steps you can take to protect your system from this vulnerability.</p> <p><strong>UPDATE</strong> September 14, 2021: Microsoft has released security updates to address this vulnerability. Please see the Security Updates table for the applicable update for your system. We recommend that you install these updates immediately. Please see the FAQ for important information about which updates are applicable to your system.</p>

Affected

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

v < 10.0.10240.1906010.0.10240.0 ≤ v < 10.0.10240.1906010.0.10240.0
Affected range stops below 10.0.10240.19060, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.465110.0.14393.0 ≤ v < 10.0.14393.465110.0.14393.0
Affected range stops below 10.0.14393.4651, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.218310.0.0 ≤ v < 10.0.17763.218310.0.0 ≤ v < 10.0.19041.123710.0.17763.0 ≤ v < 10.0.17763.218310.0.010.0.17763.0
Affected range stops below 10.0.17763.2183, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.19041.1237, so it looks safe — our inference, not a vendor statement
v < 10.0.18363.180110.0.0 ≤ v < 10.0.18363.180110.0.0
Affected range stops below 10.0.18363.1801, so it looks safe — our inference, not a vendor statement
v < 10.0.19041.123710.0.0 ≤ v < 10.0.19041.123710.0.0
Affected range stops below 10.0.19041.1237, so it looks safe — our inference, not a vendor statement
v < 10.0.19042.123710.0.0 ≤ v < 10.0.19042.123710.0.0
Affected range stops below 10.0.19042.1237, so it looks safe — our inference, not a vendor statement
v < 10.0.19043.123710.0.0 ≤ v < 10.0.19043.123710.0.0
Affected range stops below 10.0.19043.1237, so it looks safe — our inference, not a vendor statement
6.1.0 ≤ v < 6.1.7601.257126.1.0sp1
Affected range stops below 6.1.7601.25712, so it looks safe — our inference, not a vendor statement
6.3.0 ≤ v < 6.3.9600.201206.3.0
Affected range stops below 6.3.9600.20120, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

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

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

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

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-22

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