Skip to content
Server Security Center
KEVhigh8.8 Used in ransomware campaigns

CVE-2021-40444: Microsoft MSHTML Remote Code Execution

Microsoft MSHTML · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
98%
among the highest 0.1% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2021-11-17
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-40444 explained

CVE-2021-40444 is a remote code execution vulnerability in MSHTML, the browser rendering engine in Microsoft Windows. An attacker can use a malicious ActiveX control in a specially crafted Microsoft Office document. Microsoft reported targeted attacks, CISA lists it as known exploited, and it has been used in ransomware campaigns.

Impact

An attacker who convinces a user to open a malicious Office document can execute code on the system. The attack works over the network, needs no privileges and has low complexity, but requires user interaction. Users with fewer rights could be less affected than administrators. CISA rates the technical impact as total, meaning full control of the affected component, and rates exploitation as not automatable. CISA lists the vulnerability as known exploited, including in ransomware.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 1909, 2004, 20H2 and 21H1, Windows 7, Windows 7 Service Pack 1, Windows 8.1, and Windows Server 2008 R2 Service Pack 1 including Server Core. Fixed builds include 10.0.10240.19060, 10.0.14393.4651, 10.0.17763.2183, 10.0.18363.1801, 10.0.19041.1237, 10.0.19042.1237, 10.0.19043.1237, 6.3.9600.20120 and 6.1.7601.25712. The page lists 13 further products.

Written with AI from the data on this page and checked against it automatically.

Official description

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. 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. 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”. 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.

Please see the Mitigations and Workaround sections for important information about steps you can take to protect your system from this vulnerability. UPDATE 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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19060
    Fixed in
    • 10.0.10240.19060
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.4651
    Fixed in
    • 10.0.14393.4651
  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.2183
    Fixed in
    • 10.0.17763.2183
  • Microsoft Windows 10 Version 190932-bit, ARM64, x64
    Affected
    • < 10.0.18363.1801
    Fixed in
    • 10.0.18363.1801
  • Microsoft Windows 10 Version 200432-bit, ARM64, x64
    Affected
    • < 10.0.19041.1237
    Fixed in
    • 10.0.19041.1237
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.1237
    Fixed in
    • 10.0.19042.1237
  • Microsoft Windows 10 Version 21H132-bit, ARM64, x64
    Affected
    • < 10.0.19043.1237
    Fixed in
    • 10.0.19043.1237
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows 8.132-bit, ARM64, x64
    Affected
    • < 6.3.9600.20120
    Fixed in
    • 6.3.9600.20120
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.25712
    Fixed in
    • 6.1.7601.25712
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21218
    Fixed in
    • 6.0.6003.21218
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21218
    Fixed in
    • 6.0.6003.21218
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23462
    Fixed in
    • 6.2.9200.23462
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23462
    Fixed in
    • 6.2.9200.23462
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20120
    Fixed in
    • 6.3.9600.20120
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20120
    Fixed in
    • 6.3.9600.20120
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.4651
    Fixed in
    • 10.0.14393.4651
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.4651
    Fixed in
    • 10.0.14393.4651
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.2183
    Fixed in
    • 10.0.17763.2183
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.2183
    Fixed in
    • 10.0.17763.2183
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.230
    Fixed in
    • 10.0.20348.230
  • Microsoft Windows Server version 2004x64
    Affected
    • < 10.0.19041.1237
    Fixed in
    • 10.0.19041.1237
  • Microsoft Windows Server version 20H2x64
    Affected
    • < 10.0.19042.1237
    Fixed in
    • 10.0.19042.1237

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.19060
    • Microsoft Windows 10 Version 1607: 10.0.14393.4651
    • Microsoft Windows 10 Version 1809: 10.0.17763.2183
    • Microsoft Windows 10 Version 1909: 10.0.18363.1801
    • Microsoft Windows 10 Version 2004: 10.0.19041.1237
    • Microsoft Windows 10 Version 20H2: 10.0.19042.1237
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-40444
  • CISA's deadline for US federal agencies: 2021-11-17 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security updates released September 14, 2021 for each affected Windows version, per the vendor advisory.
  2. Confirm systems run at least the fixed build listed for their Windows version, such as 10.0.19043.1237 for Windows 10 Version 21H1.
  3. Keep Microsoft Defender Antivirus updated; managed environments should deploy detection build 1.349.22.0 or newer.
  4. Apply the mitigations and workarounds in the Microsoft advisory where updates cannot be installed at once.
  5. Have users work without administrative rights to reduce the impact of a successful attack.
  6. Check for signs of compromise, such as Defender for Endpoint alerts named “Suspicious Cpl File Execution”.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Questions about CVE-2021-40444

Is CVE-2021-40444 being exploited?
Yes. Microsoft reported targeted attacks using crafted Office documents. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known use in ransomware campaigns.
Do I need to do anything if automatic updates are enabled?
Microsoft states customers using automatic updates do not need extra action for the Defender detections. You should still verify that the September 14, 2021 security updates are installed on all affected systems.
How does an attack reach a system?
The attacker must convince a user to open a malicious Microsoft Office document that uses a crafted ActiveX control with the MSHTML rendering engine. Without the user opening the document, the attack does not proceed.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.