CVE-2026-21513: Microsoft MSHTML Framework Protection Mechanism Failure Vulnerability

Published Feb 10, 2026
·
Updated

Microsoft MSHTML Framework contains a protection mechanism failure vulnerability that could allow an unauthorized attacker to bypass a security feature over a network.

Other sources

MSHTML Framework Security Feature Bypass Vulnerability

Microsoft

Protection mechanism failure in MSHTML Framework allows an unauthorized attacker to bypass a security feature over a network.

Microsoft

Affected Software

70 affected componentsFixes available
Microsoft Windows
Microsoft Windows 10=1607
Microsoft Windows 11=24H2
Microsoft Windows Server 2016
Microsoft Windows Server 2025
Microsoft Windows 11=24H2
Microsoft Windows 11=23H2
Microsoft Windows 11=23H2
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows 11=25H2
Microsoft Windows 11=25H2
Microsoft Windows 10=22H2
Microsoft Windows Server 2025
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=22H2
Microsoft Windows 10 1607<10.0.14393.8868
Microsoft Windows 10 1607<10.0.14393.8868
Microsoft Windows 10 1809<10.0.17763.8389
Microsoft Windows 10 1809<10.0.17763.8389
Microsoft Windows 10 21h2<10.0.19044.6937
Microsoft Windows 10 21h2<10.0.19044.6937
Microsoft Windows 10 21h2<10.0.19044.6937
Microsoft Windows 10 22h2<10.0.19045.6937
Microsoft Windows 10 22h2<10.0.19045.6937
Microsoft Windows 10 22h2<10.0.19045.6937
Microsoft Windows 11 23h2<10.0.22631.6649
Microsoft Windows 11 23h2<10.0.22631.6649
Microsoft Windows 11 24h2<10.0.26100.7781
Microsoft Windows 11 24h2<10.0.26100.7781
Microsoft Windows 11 25h2<10.0.26200.7781
Microsoft Windows 11 25h2<10.0.26200.7781
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.8868
Microsoft Windows Server 2019<10.0.17763.8389
Microsoft Windows Server 2022<10.0.20348.4711
Microsoft Windows Server 2022 23h2<10.0.25398.2149
Microsoft Windows Server 2025<10.0.26100.32313
Microsoft Windows 11=24H2
10.0.26100.784010.0.26100.7781
Microsoft Windows 10=1607
10.0.14393.8868
Microsoft Windows 11=25H2
10.0.26200.784010.0.26200.7781
Microsoft Windows Server 2016<10.0.14393.8868
10.0.14393.8868
Microsoft Windows Server 2025<10.0.26100.32370, <10.0.26100.32313
10.0.26100.3237010.0.26100.32313
Microsoft Windows 11=23H2
10.0.22631.6649
Microsoft Windows 11=23H2
10.0.22631.6649
Microsoft Windows 11=24H2
10.0.26100.784010.0.26100.7781
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.2149
10.0.25398.2149
Microsoft Windows 11=25H2
10.0.26200.784010.0.26200.7781
Microsoft Windows Server 2025<10.0.26100.32370, <10.0.26100.32313
10.0.26100.3237010.0.26100.32313
Microsoft Windows 10=22H2
10.0.19045.6937
Microsoft Windows 10=22H2
10.0.19045.6937
Microsoft Windows 10=22H2
10.0.19045.6937
Microsoft Windows Server 2012<6.2.9200.25923
6.2.9200.25923
Microsoft Windows Server 2012 R2<6.3.9600.23022
6.3.9600.23022
Microsoft Windows Server 2012 R2<6.3.9600.23022
6.3.9600.23022
Microsoft Windows 10=21H2
10.0.19044.6937
Microsoft Windows 10=1607
10.0.14393.8868
Microsoft Windows Server 2012<6.2.9200.25923
6.2.9200.25923
Microsoft Windows 10=1809
10.0.17763.8389
Microsoft Windows 10=21H2
10.0.19044.6937
Microsoft Windows Server 2022<10.0.20348.4773, <10.0.20348.4711
10.0.20348.477310.0.20348.4711
Microsoft Windows 10=21H2
10.0.19044.6937
Microsoft Windows Server 2016<10.0.14393.8868
10.0.14393.8868
Microsoft Windows Server 2019<10.0.17763.8389
10.0.17763.8389
Microsoft Windows Server 2022<10.0.20348.4773, <10.0.20348.4711
10.0.20348.477310.0.20348.4711
Microsoft Windows 10=1809
10.0.17763.8389
Microsoft Windows 11=26H1
10.0.28000.1575
Microsoft Windows 11=26H1
10.0.28000.1575
Microsoft Windows Server 2019<10.0.17763.8389
10.0.17763.8389

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.7840Fixed in 10.0.26100.7781Patch KB5077212
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.7840Fixed in 10.0.26200.7781Patch KB5077212
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.8868Patch KB5075999
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.32370Fixed in 10.0.26100.32313Patch KB5075942
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.6649Patch KB5075941
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.2149Patch KB5075897
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.6937Patch KB5075912
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.25923Patch KB5075971
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23022Patch KB5075970
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.6937Patch KB5075912
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.8389Patch KB5075904
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.4773Fixed in 10.0.20348.4711Patch KB5075943
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.1575Patch KB5077179

Event History

Feb 10, 2026
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
Data Sourced
via Microsoft·04:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·04:00 PM
Affected Software
Updated
via Microsoft·04:00 PM
Description
CVE Published
via MITRE·05:51 PM
Data Sourced
via MITRE·05:51 PM
DescriptionSeverity
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software
News Published
via The Register·10:10 PM
News Published
via The Register·10:13 PM
Apr 29, 2026
News Published
via BleepingComputer·10:29 AM
News Published
via BleepingComputer·10:30 AM
News Published
via The Register·07:15 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21513?

CVE-2026-21513 is classified as a security feature bypass vulnerability, posing significant risk as it allows attackers to bypass protective mechanisms.

2

How do I fix CVE-2026-21513?

To fix CVE-2026-21513, apply the latest patches provided by Microsoft for the affected Windows products.

3

Which products are affected by CVE-2026-21513?

CVE-2026-21513 affects various Microsoft Windows products, including Windows Server 2016, Windows 10, and Windows 11.

4

Can CVE-2026-21513 be exploited remotely?

Yes, CVE-2026-21513 can be exploited over a network, allowing unauthorized access to bypass security features.

5

What are the common impacts of CVE-2026-21513?

The primary impact of CVE-2026-21513 is the potential unauthorized access and manipulation of system features, compromising system security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203