CVE-2024-30040: Microsoft Windows MSHTML Platform Security Feature Bypass
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-05-14.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 3.9%
- higher than 90.6% of all CVEs
- Added to CISA KEV
- 2024-05-14
- US federal due date 2024-06-04
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2024-30040 explained
CVE-2024-30040 is a security feature bypass vulnerability in the Microsoft Windows MSHTML Platform, classified as improper input validation. It affects multiple Windows 10, Windows 11 and Windows Server releases. CISA lists it as known to be exploited, so affected systems should be patched promptly.
Impact
An attacker can exploit this over the network without privileges or special conditions, but a user must take an action, such as opening attacker-supplied content. Successful exploitation can lead to high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation requires manual steps per target. Attackers are known to use it; ransomware use is unknown.
Who is affected
The CVE record lists Windows 10 Version 1507 (fixed in 10.0.10240.20651), 1809 and Windows Server 2019 including Server Core (fixed in 10.0.17763.5820), Windows 10 21H2 (10.0.19044.4412) and 22H2 (10.0.19045.4412), Windows 11 21H2 (10.0.22000.2960), 22H2 (10.0.22621.3593), 22H3 and 23H2 (10.0.22631.3593), Windows Server 2022 (10.0.20348.2461) and Windows Server 2022, 23H2 Edition Server Core (10.0.25398.887). Earlier builds are affected. Further products are listed on this page.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows MSHTML Platform contains an unspecified vulnerability that allows for a security feature bypass.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.5820
- 10.0.17763.5820
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.5820
- 10.0.17763.5820
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.5820
- 10.0.17763.5820
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.2461
- 10.0.20348.2461
- Microsoft Windows 11 version 21H2x64, ARM64AffectedFixed in
- < 10.0.22000.2960
- 10.0.22000.2960
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.4412
- 10.0.19044.4412
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.3593
- 10.0.22621.3593
- Microsoft Windows 10 Version 22H2x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19045.4412
- 10.0.19045.4412
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.3593
- 10.0.22631.3593
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.3593
- 10.0.22631.3593
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.887
- 10.0.25398.887
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.20651
- 10.0.10240.20651
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.6981
- 10.0.14393.6981
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.6981
- 10.0.14393.6981
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.6981
- 10.0.14393.6981
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows 11 version 21H2x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.5820
- Microsoft Windows Server 2019: 10.0.17763.5820
- Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.5820
- Microsoft Windows Server 2022: 10.0.20348.2461
- Microsoft Windows 11 version 21H2: 10.0.22000.2960
- Microsoft Windows 10 Version 21H2: 10.0.19044.4412
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30040
- CISA's deadline for US federal agencies: 2024-06-04 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build listed for its Windows release.
- Prioritize patching, since CISA lists this vulnerability as known to be exploited; US federal agencies had a due date of 2024-06-04.
- Verify installed build numbers across endpoints and servers to confirm the fix is applied.
- Follow the Microsoft advisory for any mitigations, and discontinue use of systems where mitigations are unavailable, as CISA requires.
- Advise users to be cautious with untrusted files and links, since exploitation requires user interaction.
- Check systems for signs of compromise where patching was delayed.
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-20 Improper Input Validation
Questions about CVE-2024-30040
- Is CVE-2024-30040 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-05-14. Whether it is used in ransomware campaigns is unknown.
- Does exploitation need user action?
- Yes. The CVSS data shows user interaction is required, but no privileges are needed and the attack can come over the network.
- How do I know if a system is fixed?
- Compare the Windows build number with the fixed version for its release, for example
10.0.22631.3593for Windows 11 Version 23H2 or10.0.20348.2461for Windows Server 2022. Lower builds are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.