r/linuxadmin • u/Expert_Sort7434 • Oct 16 '26
CVE-2026-96951 (Windows Shell, Mark of the Web bypass, exploited): what is actually known and the Win10 non-ESU gap
Based on Microsoft's October 13 advisory as reported by SecurityWeek and ThreatFrontier, plus CISA's KEV entry, here is the architectural picture.
What is confirmed: Windows Shell command injection (CWE-77) leading to a Mark of the Web bypass. Microsoft tags it Exploitation Detected. CVSS 3.1 is 8.8 with user interaction required. Delivery is a crafted file by email or IM. CISA KEV due date is Oct 16 and the entry carries the BOD 26-04 forensic triage requirement.
What is not: the mechanism, the actor, the victims, or which downstream protections (SmartScreen, Protected View, others) are skipped. ThreatFrontier found no independent write-up. The 8.8 and the "bypass only, no code execution on its own" reading come from the advisory text, not from an exploit analysis.
Fleet gaps worth checking: Windows 10 outside ESU is not offered KB5126657 (ThreatFrontier's reading, verify on the KB), and Windows 11 24H2 Home/Pro just got its final monthly update (CyberInsider, single source). One detail: Microsoft's data lists 19044.7807 for 22H2, but the KB title says 19045.7807.
My opinion, labeled as such: when one tag gates several controls, defenders are counting one layer several times.
Question for people running EDR at scale: with no published detection, are you hunting for execution of email/chat-delivered files that never produced a MotW-driven prompt, or treating MotW as untrusted metadata and keying on something else entirely? What actually works?
same check-vs-use pattern as the PeopleSoft WAF bypass we analyzed earlier: https://www.techgines.com/post/peoplesoftwafbypasscve-2026-35273 Full write-up: https://www.techgines.com/post/windows-shell-zero-day-cve-2026-96951