Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2026-21513: Microsoft MSHTML Framework Security Feature Bypass

Published Feb 10, 2026 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS8.8High · v3.1
EPSS15.9%97th percentile
CISA KEVYesAdded Feb 10, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2026-21513CWE-693 · Protection Mechanism Failure

CVE-2026-21513 is a protection mechanism failure in the Microsoft MSHTML Framework that allows a remote, unauthenticated attacker to bypass file-execution security prompts. The vulnerability affects hyperlink navigation handling in the _AttemptShellExecuteForHlinkNavigate function, where insufficient validation of navigation targets can cause resources to be passed to ShellExecuteExW outside the intended browser security context. Exploitation typically requires a user to open a crafted HTML file or Windows shortcut; observed shortcut samples contain appended HTML processed by MSHTML. The flaw can bypass restrictions on executing files from untrusted network sources and potentially enable code execution. APT28 exploited it as a zero-day, including in chains with CVE-2026-21510. Microsoft released a fix on February 10, 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation bypasses security prompts and trust restrictions associated with file execution, potentially allowing attacker-controlled local or remote resources to execute without the expected warning. In observed APT28 campaigns, chaining this vulnerability with CVE-2026-21510 bypassed Microsoft Defender SmartScreen and enabled remote execution of malicious code. Code execution is a potential consequence of the bypass and exploit chain, rather than evidence of a standalone memory-corruption vulnerability. Microsoft assigned a CVSS 3.1 base score of 8.8, and CISA included the vulnerability in its Known Exploited Vulnerabilities catalog.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific vendor workaround is identified. Until updates are deployed, avoid opening untrusted HTML files and Windows shortcuts received through email attachments, links, or downloads. Monitor unexpected child processes and execution activity originating from document-handling applications, and restrict unnecessary outbound connections to reduce payload retrieval opportunities. Avoiding the Internet Explorer browser alone does not eliminate exposure because other Windows applications can invoke MSHTML.

Remediation

Patch, then assume compromise.

Apply Microsoft's official security update for CVE-2026-21513, released with the February 10, 2026 Windows security updates, or an applicable superseding update. Validate deployment across affected workstations and servers, prioritizing exposed and high-risk systems because exploitation is confirmed. Exact affected builds, update identifiers, and minimum fixed versions are not available in the supplied vulnerability details. Investigate suspected exploitation separately; patching does not remove an existing compromise.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2026-21513 exploited in the wild?
Yes. As of Nov 14, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 10, 2026.
Is there a public exploit for CVE-2026-21513?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-21513.
Is there a patch for CVE-2026-21513?
Apply Microsoft's official security update for CVE-2026-21513, released with the February 10, 2026 Windows security updates, or an applicable superseding update. Validate deployment across affected workstations and servers, prioritizing exposed and high-risk systems because exploitation is confirmed.
What products are affected by CVE-2026-21513?
Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 11 more.
How severe is CVE-2026-21513?
CVE-2026-21513 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 15.9% (97th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

183 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+57 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence30Every report linking this CVE to a named adversary.
Associated malware12Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity115Community discussion across Reddit, Mastodon, and other social sources.