CVE-2026-96951: Windows Shell Mark of the Web Bypass Is Being Exploited—Install the October Update
On October 13, 2026, Microsoft fixed an already exploited Windows Shell vulnerability (CVE-2026-96951, CVSS 8.8). Crafted files delivered by email or chat can bypass Mark of the Web protection. CISA lists the vulnerability in its KEV catalog; only the cumulative October update resolves it.
On October 13, 2026, Microsoft closed a Windows Shell vulnerability in its monthly security updates that is already being used in attacks. The vulnerability is identified as CVE-2026-96951, and Microsoft rates it as “Important” with a CVSS score of 8.8. An attacker sends a crafted file by email or instant message; if the victim opens it, Mark of the Web (MotW) protection does not apply. Microsoft reports detected exploitation, and the U.S. agency CISA added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog the same day. Updates are available for all listed Windows versions; Microsoft does not list a workaround.
Support with updates and verification
If you need help securing systems, checking for compromise, or updating Windows clients and servers, please use the contact form on adeptio.ch. I can also get back to you on short notice.
Key facts at a glance
| Attribute | Details |
|---|---|
| Advisory | Microsoft Security Update Guide, CVE-2026-96951 “Windows Shell Security Feature Bypass Vulnerability,” published October 13, 2026 |
| CVE | CVE-2026-96951 |
| Rating | CVSS 3.1: 8.8 (high), Microsoft rating “Important,” AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H; temporal 8.2 with E:F/RL:O/RC:C |
| Vulnerability type | Command injection (CWE-77) in the Windows Shell, Mark of the Web bypass |
| Prerequisite | no authentication; the victim must open a crafted file or click a link |
| Affected versions | Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), Windows Server 2012 R2, 2016, 2019, 2022, and 2025; Microsoft also lists Outlook.com |
| Fixed versions | Cumulative updates from October 13, 2026; see table below |
| Exploitation | detected according to Microsoft (“Exploitation Detected”), not publicly known in advance; CISA KEV since October 13, 2026 |
| CISA deadline (U.S. federal agencies) | October 16, 2026 |
| Workaround | none published |
Affected versions and updates
The information comes from Microsoft’s Security Update Guide. In each case, every build below the listed build is affected.
| Version branch | Affected | Fixed |
|---|---|---|
| Windows 11 26H2 (x64, ARM64) | Build below 10.0.26300.9711 | KB5127648, Build 10.0.26300.9711 |
| Windows 11 26H1 (x64, ARM64) | Build below 10.0.28000.3231 | KB5127646, Build 10.0.28000.3231 |
| Windows 11 25H2 (x64, ARM64) | Build below 10.0.26200.9711 | KB5127648, Build 10.0.26200.9711 |
| Windows 11 24H2 (x64, ARM64) | Build below 10.0.26100.9711 | KB5127648, Build 10.0.26100.9711 |
| Windows 11 23H2 (x64, ARM64) | Build below 10.0.22631.7652 | KB5126653, Build 10.0.22631.7652 |
| Windows 10 22H2 (ESU) | Build below 10.0.19045.7807 | KB5126657, Build 10.0.19045.7807 |
| Windows 10 21H2 | Build below 10.0.19044.7807 | KB5126657, Build 10.0.19044.7807 |
| Windows 10 1809 | Build below 10.0.17763.9376 | KB5126651, Build 10.0.17763.9376 |
| Windows 10 1607 | Build below 10.0.14393.9612 | KB5126868, Build 10.0.14393.9612 |
| Windows Server 2025 (including Server Core) | Build below 10.0.26100.33650 | KB5126646, Build 10.0.26100.33650 |
| Windows Server 2022 (including Server Core) | Build below 10.0.20348.5761 | KB5126655, Build 10.0.20348.5761 |
| Windows Server 2019 (including Server Core) | Build below 10.0.17763.9376 | KB5126651, Build 10.0.17763.9376 |
| Windows Server 2016 (including Server Core) | Build below 10.0.14393.9612 | KB5126868, Build 10.0.14393.9612 |
| Windows Server 2012 R2 (ESU, including Server Core) | Build below 6.3.9600.23470 | KB5126836, Build 6.3.9600.23470 |
| Outlook.com | before 20260925.100 | Version 20260925.100 according to the release notes |
For Windows 10 22H2, the Security Update Guide lists build 10.0.19044.7807. Microsoft’s KB page, however, lists KB5126657 with build 19045.7807 for 22H2 and 19044.7807 for 21H2; the table follows the KB page. Windows 10 22H2 and Windows Server 2012 R2 appear in the Security Update Guide only as ESU entries. Devices without Extended Security Updates do not receive the update and remain vulnerable.
For Outlook.com, Microsoft provides no further details beyond version number 20260925.100 and a reference to the release notes.
Whether the update is installed can be checked Get-HotFix locally or across multiple computers:
Get-HotFix -Id KB5126655 -ComputerName srv01.example.com, srv02.example.com
If the command returns no result for a computer, the update is missing there. Get-HotFix reads the WMI class Win32_QuickFixEngineering and displays only updates installed through Component Based Servicing.
What is known about exploitation
In the advisory FAQ, Microsoft describes an attack scenario via email or instant message: The attacker sends the victim a crafted file. The attacker cannot force the victim to open the file and must persuade them to click a link or open an attachment. The result is a Mark of the Web bypass. Mark of the Web is the marker Windows attaches to files from the internet; according to CrowdStrike’s analysis, it triggers, among other things, Protected View in Office and the SmartScreen warning for downloaded programs.
Microsoft classifies the vulnerability as exploited and not publicly known before Patch Tuesday. According to Tenable, it is the third exploited Windows Shell vulnerability this year, after CVE-2026-21510 (February) and CVE-2026-32202 (April).
As of October 14, 2026, no public information is available about attackers, campaigns, targets, file types used, or indicators. CISA lists use by ransomware groups as “Unknown.”
Immediate actions
-
Install the update: Install the cumulative October update from the table on all Windows clients and servers, then restart them. Microsoft requires a restart for all entries. Clients with email and chat access should be addressed first because the described attack scenario targets them.
-
Verify installation status: Use
Get-HotFixor your own update management to confirm that the update is installed on all devices, and remediate outliers. -
Address systems without updates: Windows 10 22H2 and Windows Server 2012 R2 without ESU do not receive the update. Enroll these devices in the ESU program, upgrade them to a supported version, or disconnect them from email and chat traffic.
-
Reduce exposure: Since Microsoft does not list a workaround, the only option until the update is installed is to make delivery of crafted files more difficult. Filtering attachments at the mail gateway or in Exchange Online Protection and checking links reduce the number of files that reach users at all. Users should be informed that attacks involving crafted attachments are currently underway.
Checking for compromise
As of October 14, 2026, Microsoft, CISA, and the reviewed analyses do not list any indicators (file names, hashes, IP addresses, or domains). A targeted search for this vulnerability is therefore not possible. In addition to installing the update, CISA requires U.S. federal agencies to perform forensic triage according to the requirements of BOD 26-04.
The update closes the vulnerability but does not undo malware that has already run. The following are therefore advisable:
-
Review alerts from the endpoint security solution (such as Microsoft Defender for Endpoint) from recent weeks for files launched from email attachments, chat messages, or downloads.
-
Review mail gateway and quarantine logs for attachments and links that users reported or released despite warnings.
-
Isolate suspicious devices and preserve logs before remediation so that forensic analysis remains possible.
-
Monitor the advisory: If Microsoft updates the advisory or a security company publishes indicators, repeat the search using them.
Assessment
The Windows Shell is part of every Windows installation; CrowdStrike therefore counts virtually the entire Windows base among the affected systems. The attack scenario relies on the user: An attachment or link delivered by email or chat is enough if the victim opens it. Mark of the Web underpins several Windows and Office security features; a bypass removes warnings users would otherwise see before opening a file. No notice from the National Cyber Security Centre (NCSC) or other European CERTs regarding CVE-2026-96951 could be found as of October 14, 2026.
Comments
Comments are loaded from GitHub / Giscus.