CVE-2026-21513: Microsoft MSHTML Framework Protection Mechanism Failure
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2026-02-10.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 16%
- higher than 96.9% of all CVEs
- Added to CISA KEV
- 2026-02-10
- US federal due date 2026-03-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-21513 explained
CVE-2026-21513 is a protection mechanism failure in the MSHTML Framework in Microsoft Windows. It lets an unauthorized attacker bypass a security feature over a network. CISA lists it as known to be exploited, so affected Windows client and server systems should be patched promptly.
Impact
An attacker needs no privileges and can act over the network, but a user must interact, for example by opening attacker-supplied content. Successful exploitation bypasses a Windows security feature. Confidentiality, integrity and availability impacts are rated high. CISA rates the technical impact as total and the vulnerability as not automatable, so mass exploitation without manual steps is less likely. Attackers are known to use it. Ransomware use is unknown.
Who is affected
The CVE record lists Windows 10 Version 1607 (fixed in 10.0.14393.8868), 1809 (10.0.17763.8389), 21H2 (10.0.19044.6937) and 22H2 (10.0.19045.6937). It lists Windows 11 version 22H3 and 23H2 (10.0.22631.6649), 24H2 (10.0.26100.7840), 25H2 (10.0.26200.7840) and 26H1 (10.0.28000.1575). Server entries are Windows Server 2012, including Server Core (6.2.9200.25923), and Server 2012 R2 (6.3.9600.23022). Earlier builds are affected. Further products are listed on the page.
Written with AI from the data on this page and checked against it automatically.
Official description
Protection mechanism failure in MSHTML Framework allows an unauthorized attacker to bypass a security feature over a network.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, 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 160732-bit, x64AffectedFixed in
- < 10.0.14393.8868
- 10.0.14393.8868
- Microsoft Windows 10 Version 180932-bit, x64AffectedFixed in
- < 10.0.17763.8389
- 10.0.17763.8389
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.6937
- 10.0.19044.6937
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.6937
- 10.0.19045.6937
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.6649
- 10.0.22631.6649
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.6649
- 10.0.22631.6649
- Microsoft Windows 11 Version 24H2ARM64, x64AffectedFixed in
- < 10.0.26100.7840
- 10.0.26100.7840
- Microsoft Windows 11 Version 25H2AffectedFixed in
- < 10.0.26200.7840
- 10.0.26200.7840
- Microsoft Windows 11 version 26H1ARM64AffectedFixed in
- < 10.0.28000.1575
- 10.0.28000.1575
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.25923
- 6.2.9200.25923
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 11 Version 24H2ARM64, x64 |
|
|
| Microsoft Windows 11 Version 25H2 |
|
|
| Microsoft Windows 11 version 26H1ARM64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
Show 11 more products
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.25923
- 6.2.9200.25923
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.23022
- 6.3.9600.23022
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.23022
- 6.3.9600.23022
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.8868
- 10.0.14393.8868
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.8868
- 10.0.14393.8868
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.8389
- 10.0.17763.8389
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.8389
- 10.0.17763.8389
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.4773
- 10.0.20348.4773
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.2149
- 10.0.25398.2149
- Microsoft Windows Server 2025x64AffectedFixed in
- < 10.0.26100.32370
- 10.0.26100.32370
- Microsoft Windows Server 2025 (Server Core installation)x64AffectedFixed in
- < 10.0.26100.32370
- 10.0.26100.32370
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2025x64 |
|
|
| Microsoft Windows Server 2025 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1607: 10.0.14393.8868
- Microsoft Windows 10 Version 1809: 10.0.17763.8389
- Microsoft Windows 10 Version 21H2: 10.0.19044.6937
- Microsoft Windows 10 Version 22H2: 10.0.19045.6937
- Microsoft Windows 11 version 22H3: 10.0.22631.6649
- Microsoft Windows 11 Version 23H2: 10.0.22631.6649
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21513
- CISA's deadline for US federal agencies: 2026-03-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to at least the fixed build listed for its Windows version.
- Prioritize internet-facing endpoints and systems whose users open web content, email or downloaded files.
- Follow the Microsoft advisory and apply any mitigations it describes on systems you cannot patch at once.
- Federal agencies must apply the fix or mitigations by 2026-03-03, as CISA requires.
- Remind users not to open untrusted links or files, since exploitation requires user interaction.
- Check systems for signs of compromise, because attackers are known to exploit this vulnerability.
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-693 Protection Mechanism Failure
Questions about CVE-2026-21513
- Is CVE-2026-21513 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-10. Whether ransomware groups use it is unknown.
- Can it be exploited without user action?
- No. The CVSS vector says user interaction is required, and CISA rates it as not automatable. No privileges are needed, and the attack works over a network.
- What should we do if we cannot patch right away?
- Apply the mitigations in the Microsoft advisory. CISA's required action is to apply vendor mitigations, follow BOD 22-01 guidance for cloud services, or stop using the product if mitigations are unavailable.
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-21. Always confirm with the vendor's or distribution's advisory before patching.