14 October 2026 6 min read

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

AttributeDetails
AdvisoryMicrosoft Security Update Guide, CVE-2026-96951 “Windows Shell Security Feature Bypass Vulnerability,” published October 13, 2026
CVECVE-2026-96951
RatingCVSS 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 typeCommand injection (CWE-77) in the Windows Shell, Mark of the Web bypass
Prerequisiteno authentication; the victim must open a crafted file or click a link
Affected versionsWindows 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 versionsCumulative updates from October 13, 2026; see table below
Exploitationdetected 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
Workaroundnone 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 branchAffectedFixed
Windows 11 26H2 (x64, ARM64)Build below 10.0.26300.9711KB5127648, Build 10.0.26300.9711
Windows 11 26H1 (x64, ARM64)Build below 10.0.28000.3231KB5127646, Build 10.0.28000.3231
Windows 11 25H2 (x64, ARM64)Build below 10.0.26200.9711KB5127648, Build 10.0.26200.9711
Windows 11 24H2 (x64, ARM64)Build below 10.0.26100.9711KB5127648, Build 10.0.26100.9711
Windows 11 23H2 (x64, ARM64)Build below 10.0.22631.7652KB5126653, Build 10.0.22631.7652
Windows 10 22H2 (ESU)Build below 10.0.19045.7807KB5126657, Build 10.0.19045.7807
Windows 10 21H2Build below 10.0.19044.7807KB5126657, Build 10.0.19044.7807
Windows 10 1809Build below 10.0.17763.9376KB5126651, Build 10.0.17763.9376
Windows 10 1607Build below 10.0.14393.9612KB5126868, Build 10.0.14393.9612
Windows Server 2025 (including Server Core)Build below 10.0.26100.33650KB5126646, Build 10.0.26100.33650
Windows Server 2022 (including Server Core)Build below 10.0.20348.5761KB5126655, Build 10.0.20348.5761
Windows Server 2019 (including Server Core)Build below 10.0.17763.9376KB5126651, Build 10.0.17763.9376
Windows Server 2016 (including Server Core)Build below 10.0.14393.9612KB5126868, Build 10.0.14393.9612
Windows Server 2012 R2 (ESU, including Server Core)Build below 6.3.9600.23470KB5126836, Build 6.3.9600.23470
Outlook.combefore 20260925.100Version 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
Options explained
OptionEffect
-Idfilters for the specified KB number; here, the Windows Server 2022 update is used as an example—use the KB from the table for other versions
-ComputerNamequeries the specified computers; without the parameter, the query applies to the local computer

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

  1. 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.

  2. Verify installation status: Use Get-HotFix or your own update management to confirm that the update is installed on all devices, and remediate outliers.

  3. 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.

  4. 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:

  1. 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.

  2. Review mail gateway and quarantine logs for attachments and links that users reported or released despite warnings.

  3. Isolate suspicious devices and preserve logs before remediation so that forensic analysis remains possible.

  4. 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.

Sources

  1. Microsoft Security Update Guide: CVE-2026-96951

    Advisory with CVSS vector, exploitation status, FAQ on the attack scenario, affected products, KB numbers, and builds.

    https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96951
  2. NVD: CVE-2026-96951

    Description, CWE-77, Microsoft CVSS rating, and KEV data; status “Undergoing Analysis.”

    https://nvd.nist.gov/vuln/detail/CVE-2026-96951
  3. CISA: Known Exploited Vulnerabilities Catalog, CVE-2026-96951

    KEV entry with addition on October 13, 2026, deadline of October 16, 2026, and reference to BOD 26-04.

    https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96951
  4. CISA: CISA Adds Two Known Exploited Vulnerabilities to Catalog
  5. Microsoft Support: KB5126657

    October update for Windows 10 with builds 19045.7807 (22H2) and 19044.7807 (21H2).

    https://support.microsoft.com/help/5126657
  6. Tenable: Microsoft’s October 2026 Patch Tuesday addresses 1407 CVEs (CVE-2026-96951)

    Analysis covering the attack scenario and previously exploited Windows Shell vulnerabilities in 2026.

    https://www.tenable.com/blog/microsofts-october-2026-patch-tuesday-addresses-1407-cves-cve-2026-96951
  7. CrowdStrike: October 2026 Patch Tuesday

    Assessment of Mark of the Web, Protected View, and SmartScreen.

    https://www.crowdstrike.com/en-us/blog/patch-tuesday-analysis-october-2026/
  8. Krebs on Security: Microsoft Patches More Than 1,400 Security Flaws

    Report from October 13, 2026, identifying CVE-2026-96951 as the only exploited vulnerability of that Patch Tuesday.

    https://krebsonsecurity.com/2026/10/microsoft-patches-more-than-1400-security-flaws/
  9. Microsoft Learn: Get-HotFix

    Documentation of the cmdlet with the parameters -Id and -ComputerName.

    https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-hotfix

Comments

Comments are loaded from GitHub / Giscus.