Skip to content

CVE-2021-40444

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.

CVSS
8.8Highscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 3 Nov 2021CISA deadline for US federal agencies: 17 Nov 2021known use in ransomware campaignspublic exploit code
EPSS
97.8%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
15 Sept 2021analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Microsoft Windows 10 Version 1507>= 10.0.10240.0 and < 10.0.10240.19060Vendor says fixed in: not stated
Microsoft Windows 10 Version 1607>= 10.0.14393.0 and < 10.0.14393.4651Vendor says fixed in: not stated
Microsoft Windows 10 Version 1809>= 10.0.17763.0 and < 10.0.17763.2183>= 10.0.0 and < 10.0.17763.2183Vendor says fixed in: not stated
Microsoft Windows 10 Version 1909>= 10.0.0 and < 10.0.18363.1801Vendor says fixed in: not stated
Microsoft Windows 10 Version 2004>= 10.0.0 and < 10.0.19041.1237Vendor says fixed in: not stated
Microsoft Windows 10 Version 20H2>= 10.0.0 and < 10.0.19042.1237Vendor says fixed in: not stated
Microsoft Windows 10 Version 21H1>= 10.0.0 and < 10.0.19043.1237Vendor says fixed in: not stated
Microsoft Windows 7>= 6.1.0 and < 6.1.7601.25712Vendor says fixed in: not stated
Microsoft Windows 7 Service Pack 1>= 6.1.0 and < 6.1.7601.25712Vendor says fixed in: not stated
Microsoft Windows 8.1>= 6.3.0 and < 6.3.9600.20120Vendor says fixed in: not stated
Microsoft Windows Server 2008 R2 Service Pack 1>= 6.1.7601.0 and < 6.1.7601.25712Vendor says fixed in: not stated
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)>= 6.1.7601.0 and < 6.1.7601.25712Vendor says fixed in: not stated
Microsoft Windows Server 2008 Service Pack 2>= 6.0.6003.0 and < 6.0.6003.21218Vendor says fixed in: not stated
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)>= 6.0.6003.0 and < 6.0.6003.21218Vendor says fixed in: not stated
Microsoft Windows Server 2012>= 6.2.9200.0 and < 6.2.9200.23462Vendor says fixed in: not stated
Microsoft Windows Server 2012 R2>= 6.3.9600.0 and < 6.3.9600.20120Vendor says fixed in: not stated
Microsoft Windows Server 2012 R2 (Server Core installation)>= 6.3.9600.0 and < 6.3.9600.20120Vendor says fixed in: not stated
Microsoft Windows Server 2012 (Server Core installation)>= 6.2.9200.0 and < 6.2.9200.23462Vendor says fixed in: not stated
Microsoft Windows Server 2016>= 10.0.14393.0 and < 10.0.14393.4651Vendor says fixed in: not stated
Microsoft Windows Server 2016 (Server Core installation)>= 10.0.14393.0 and < 10.0.14393.4651Vendor says fixed in: not stated
Microsoft Windows Server 2019>= 10.0.17763.0 and < 10.0.17763.2183Vendor says fixed in: not stated
Microsoft Windows Server 2019 (Server Core installation)>= 10.0.17763.0 and < 10.0.17763.2183Vendor says fixed in: not stated
Microsoft Windows Server 2022>= 10.0.20348.0 and < 10.0.20348.230Vendor says fixed in: not stated
Microsoft Windows Server version 2004>= 10.0.0 and < 10.0.19041.1237Vendor says fixed in: not stated
Microsoft Windows Server version 20H2>= 10.0.0 and < 10.0.19042.1237Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • microsoft:windows_10_1507
  • microsoft:windows_10_1607
  • microsoft:windows_10_1809
  • microsoft:windows_10_1909
  • microsoft:windows_10_2004
  • microsoft:windows_10_20h2
  • microsoft:windows_10_21h1
  • microsoft:windows_7
  • microsoft:windows_8.1
  • microsoft:windows_rt_8.1
  • microsoft:windows_server_2004
  • microsoft:windows_server_2008
  • microsoft:windows_server_2012
  • microsoft:windows_server_2016
  • microsoft:windows_server_2019
  • microsoft:windows_server_2022
  • microsoft:windows_server_20h2

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack requires the victim to open a specially crafted Microsoft Office document containing a malicious ActiveX control. This is not delivered via an HTTP request but through a local user action of opening a file. A web application firewall only sees HTTP traffic, so it is not on this attack's path.

Also consider: canonical path validation

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 3 Nov 2021. Known use in ransomware campaigns.
CISA due date
17 Nov 2021, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Yes: 1 Metasploit module · 35 GitHub proofs of concept
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 8 Sept 2021 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Metasploit

GitHub proofs of concept

and 31 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 8 Sept 2021First public exploit or proof of concept
  2. 8 Sept 2021CISA SSVC assessment: exploitation activesame day later
  3. 15 Sept 2021Published8 days later
  4. 3 Nov 2021Added to CISA KEV (exploited in the wild)48 days later
  5. 17 Nov 2021CISA remediation due date (US federal agencies)14 days later
  6. 10 Aug 2026CVE record last updated1,728 days (about 5 years) later
  7. 12 Nov 2026Analysed by vulneraibility.com94 days (about 3 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionRequiredA victim must click, open or otherwise cooperate.
ScopeChangedImpact crosses a security boundary into other components.
ConfidentialityLowPartial data disclosure.
IntegrityHighComplete modification possible.
AvailabilityLowPartial degradation possible.

Common questions

Is CVE-2021-40444 being exploited?

Yes. CVE-2021-40444 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2021-40444?

CVE-2021-40444 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2021-40444?

Yes. A fix has been recorded for CVE-2021-40444. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2021-40444 affect?

CVE-2021-40444 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_1909, and 13 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

6 references in the CVE record, grouped by the tags the record gives them.

Patches (1)

Other links (5)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com