Windows Shell Mark of the Web Security Feature Bypass
CVE-2026-96951 is a command-injection vulnerability in Microsoft Windows Shell caused by improper neutralization of special elements used in a command. An unauthenticated remote attacker can exploit the flaw to bypass Mark of the Web (MOTW) protections by persuading a user to open or otherwise interact with specially crafted content. Affected products include Windows 10, multiple Windows 11 releases, Windows Server editions from 2012 R2 through 2025, and Outlook.com before its service-side correction. Microsoft addressed the vulnerability on October 13, 2026, after exploitation had been detected. It is rated Important by Microsoft, with a CVSS v3.1 base score of 8.8. The precise vulnerable function and observed exploitation chain have not been publicly disclosed.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation bypasses MOTW defenses that identify externally sourced files and support security warnings and protective restrictions. This removes a security barrier against malicious content and can facilitate subsequent payload execution through phishing or other file-delivery attacks. The confirmed vulnerability outcome is a security-feature bypass, not standalone remote code execution. Although the CVSS assessment assigns high potential confidentiality, integrity, and availability impacts, downstream compromise depends on the delivered content and the remainder of the attack chain. Exploitation in the wild is confirmed.
If you can’t patch tonight, do this now.
No Microsoft vulnerability-specific workaround is identified. Until patching is complete, restrict suspicious attachments, links, executable content, scripts, and archives through email and web filtering. Maintain application control, attack surface reduction policies, endpoint protection, and restrictions on execution from user-writable locations. Retain SmartScreen and other available protections, but do not rely solely on MOTW warnings. Correlate recent file deliveries and downloads with unusual child processes from Windows Explorer or document applications, script-interpreter execution, and subsequent network activity. These controls reduce exposure or aid detection; they do not correct the flaw.
Patch, then assume compromise.
Install the applicable Microsoft security updates released on October 13, 2026, or later updates that supersede them. Use Microsoft's Security Update Guide to select the correct update for each affected Windows product, release, edition, and architecture. Prioritize workstations and servers whose users handle email attachments, instant messages, or web downloads because exploitation is confirmed. Complete any required restart and verify the installed update and corrected operating-system build. Microsoft applies the Outlook.com correction service-side without requiring customer patch installation.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
106 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.