Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Microsoft MSHTML Framework Security Feature Bypass

IdentifiersCVE-2026-21513CWE-693· Protection Mechanism Failure

CVE-2026-21513 is a high-severity security feature bypass vulnerability in the Microsoft MSHTML Framework / Internet Explorer rendering engine. Microsoft describes it as a protection mechanism failure that allows an unauthorized attacker to bypass a security feature over a network. Supporting reporting indicates the vulnerable logic is in MSHTML hyperlink navigation handling within ieframe.dll, where insufficient validation of a target URL can allow attacker-controlled input to reach ShellExecuteExW and cause local or remote resources to be executed outside the intended browser security context. In observed exploitation, attackers used crafted HTML content and malicious Windows Shortcut (.lnk) files, including LNK files with embedded HTML payloads, to manipulate browser and Windows Shell handling, bypass execution prompts and trust boundaries such as Mark-of-the-Web and Internet Explorer Enhanced Security Configuration. Microsoft and third-party reporting state the flaw was exploited as a zero-day in the wild, including in campaigns attributed to APT28/Fancy Bear targeting Ukraine and EU member states beginning in late 2025.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows an attacker to bypass file execution prompts and other browser or OS trust protections for content originating from untrusted network sources. Reporting indicates this can downgrade the security context and potentially lead to remote code execution by causing the operating system to execute attacker-controlled local or remote resources outside the browser sandbox. In observed attack chains, CVE-2026-21513 was used with malicious LNK or HTML files to bypass protections including Defender SmartScreen and facilitate silent multi-stage payload delivery and execution on victim systems.

Mitigation

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

If immediate patching is not possible, reduce exposure by preventing users from opening untrusted HTML and especially .lnk files delivered via email, links, or downloads; harden email and web filtering to block malicious shortcut and HTML attachments; and increase monitoring for suspicious LNK execution, MSHTML invocation, ShellExecute-related child process creation, and outbound connections associated with staged payload delivery. Because observed exploitation relied on phishing-delivered files and trust-boundary bypass, user-facing controls around attachment handling and download execution can reduce risk until patches are applied.

Remediation

Patch, then assume compromise.

Apply Microsoft's February 2026 security update for CVE-2026-21513 on all affected Windows systems. Prioritize patching because Microsoft and CISA reported active exploitation and CISA added the vulnerability to the KEV catalog. Validate deployment across supported Windows versions, including affected Windows 10 builds referenced in the content, and review systems for signs of compromise where exploitation may have occurred before patching.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence26

Every observed campaign linking this CVE to a named adversary.

Associated malware9

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity110

Community discussion across Reddit, Mastodon, and other social sources.