Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-21510: Windows Shell SmartScreen and Security Prompt Bypass

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

CVE-2026-21510 is a protection mechanism failure in Microsoft Windows Shell that allows an unauthenticated remote attacker to bypass Microsoft Defender SmartScreen and Shell security prompts by convincing a user to open a malicious link or Windows shortcut. The demonstrated exploit abuses Shell namespace parsing through a crafted shortcut target structure referencing a remote Control Panel component, allowing an attacker-controlled DLL to load without proper network-zone validation or expected security warnings. The vulnerability has a CVSS score of 8.8 and was exploited by APT28 alongside CVE-2026-21513. Microsoft released a fix in February 2026, but a residual authentication-coercion weakness required a separate fix tracked as CVE-2026-32202.

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 checks intended to warn users before executing untrusted content, enabling attacker-controlled code to execute without additional warnings or consent after the initial user interaction. This can compromise confidentiality, integrity, and availability on the affected system. Active exploitation includes APT28 campaigns targeting Ukraine and European Union countries and TA406 campaigns chaining the vulnerability with CVE-2026-21509.

Mitigation

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

No specific vendor workaround is identified. Until updates are deployed, use email and web filtering to restrict delivery of untrusted shortcut files and malicious links, and warn users against opening them. Maintain applicable SmartScreen and Mark-of-the-Web policies, but do not rely on these controls alone because the vulnerability bypasses their expected protections. Increase monitoring for suspicious shortcut-driven execution and remote payload loading.

Remediation

Patch, then assume compromise.

Apply Microsoft's security updates addressing CVE-2026-21510, originally released on February 10, 2026, or applicable superseding cumulative updates. Also ensure that the April 14, 2026 fix for CVE-2026-32202, or a superseding update, is installed: the February fix blocked the original code-execution and SmartScreen-bypass path but left a separate authentication-coercion weakness. Validate update deployment across affected workstations and servers, and investigate potential compromise where exploitation may have preceded patching.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-21514_CVE-2026-21510This repository is a small exploit-builder project with 4 files: a license, a README, and two Python scripts. It is not a scanner or detector; it generates malicious artifacts for a document-based exploit chain targeting CVE-2026-21514 and CVE-2026-21510. Structure and purpose: - README.md documents the intended exploit chain and experimentation notes. It describes a Protected View/SBX bypass component and an RCE component, including CLSID changes, XML/object changes, and possible DLL-to-CPL substitution. - gen_rtf.py builds exploit.rtf by inserting a UTF-16-style null-padded UNC/WebDAV path into a large hardcoded RTF/OLE blob. The embedded path is \\127.0.0.1@80/final.lnk, indicating the document is meant to cause retrieval of a remote LNK over port 80 via WebDAV-like UNC syntax. - make_lnk.py builds final.lnk from hardcoded hex templates plus a null-padded remote payload path. The referenced payload path is \\127.0.0.1\cc.dll. The script comments explicitly suggest generating the DLL with msfvenom using windows/meterpreter/reverse_tcp. Main exploit capabilities: - Generates a malicious RTF lure document. - Embeds a remote UNC/WebDAV path to a malicious LNK file. - Generates a malicious LNK that references a remote DLL payload over SMB/UNC. - Includes embedded HTML/JavaScript/ActiveX logic inside the LNK data, apparently to trigger file/URL handling and object loading behavior. - Supports straightforward operator customization by changing the hardcoded remote paths and replacing the DLL payload. Operationally, this is an exploit builder rather than a full delivery framework. The payload is basic and hardcoded, so OPERATIONAL is the best fit rather than WEAPONIZED. The code is clearly intended to achieve code execution on a vulnerable Windows/Office target by chaining remote file retrieval and DLL loading.ChaitanyaHaritash · Disclosed May 4, 2026 · python · markdown · file · network · webOperationalEpSiLoNPoInTlnkRepository is a small standalone Python exploit generator consisting primarily of one large script, lnkstomperpoint.py, plus a README and .gitignore. The script is not a scanner or detector; it is an offensive utility that programmatically builds crafted Windows .lnk files purportedly targeting CVE-2026-21510, a Windows Shell Link remote code execution issue. Based on the visible code and README, its core purpose is to generate malicious shortcut files with attacker-controlled target executable, arguments, working directory, and multiple Shell Link ExtraData structures. Main capabilities described and partially evidenced in code include: LNK stomping variants, manipulation of Shell Link flags and CLSIDs, KnownFolder and PropertyStore data block generation, environment variable blocks, argument obfuscation, optional embedded payload handling, AES encryption support via pycryptodome, anti-forensics options, randomized metadata/CLSID/KnownFolder values, and generation of multiple variants for signature evasion. The script imports AES, padding, random byte generation, struct handling, and logging, indicating real implementation effort rather than a placeholder. Logging is configured to write to cve_2026_21510_ultimate_absolute.log. The visible tail of the script shows a CLI workflow that instantiates an exploit object with many offensive options and writes a generated .lnk file. The README documents extensive CLI options such as --target, --args, --output, --working-dir, --embed-payload, --encrypt-payload, --anti-forensics, --randomize-clsid, --randomize-known-folder, --obfuscate-arguments, and --generate-variants. Example usage demonstrates launching cmd.exe with /c calc.exe, embedding a payload file, and using powershell.exe with a Net.WebClient DownloadString call to retrieve a remote script from http://evil.com/shellcode.ps1. That example introduces a clear web/network-capable second stage, although the generator itself mainly produces a file-based initial vector. Overall, this repository is a standalone operational exploit builder for malicious Windows shortcut generation. Its structure is simple, but the single Python file appears feature-rich and focused on producing obfuscated, evasive .lnk payloads for execution on Windows targets.EpSiLoNPoInTOrI · Disclosed May 9, 2026 · python · markdown · file · local · webOperationalCVE-2026-32202Repository contains a single Python proof-of-concept script and a detailed README. The main file, CVE-2026-32202.py, is a research-oriented generator for crafted Windows .lnk files that reproduce the LinkTargetIDList structure associated with CVE-2026-21510 / CVE-2026-32202. The script reconstructs three shell items: (1) a Control Panel root CLSID item, (2) an 'All Control Panel Items' category item, and (3) a Unicode _IDCONTROLW structure containing a user-supplied module path, typically a UNC path to a remote .cpl file. It exposes CLI options for the embedded UNC/local path, output filename, applet ID, display name, infotip, and optional hex dump suppression. The exploit capability is file generation rather than direct network communication; however, the generated LNK is intended to cause Windows Explorer/shell32 to access the embedded UNC path during rendering, which can coerce outbound SMB authentication or connection to an attacker-controlled share. The README provides reverse-engineering context, structure layouts, call-chain analysis, and explains that the vulnerable behavior occurs before later trust verification stages. Overall, this is a focused PoC/research tool for crafting malicious shortcut files to reproduce Windows shell path-resolution behavior, not a full weaponized framework or post-exploitation implant.virus-or-not · Disclosed Apr 30, 2026 · python · markdown · file · network · wirelessPoC
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-21510 exploited in the wild?
Yes. As of Oct 20, 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-21510?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-21510, the earliest disclosed Apr 30, 2026.
Is there a patch for CVE-2026-21510?
Apply Microsoft's security updates addressing CVE-2026-21510, originally released on February 10, 2026, or applicable superseding cumulative updates. Also ensure that the April 14, 2026 fix for CVE-2026-32202, or a superseding update, is installed: the February fix blocked the original code-execution and SmartScreen-bypass path but left a separate authentication-coercion weakness.
What products are affected by CVE-2026-21510?
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-21510?
CVE-2026-21510 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 61.2% (99th percentile) as of Oct 20, 2026.
Activity feed

Recent activity

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

View more in app →
+41 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 evidence15Every report linking this CVE to a named adversary.
Associated malwareMalware 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 activity62Community discussion across Reddit, Mastodon, and other social sources.