CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Windows Shell Mark of the Web security feature bypass (CVSS 8.8), exploited zero-day fixed in the 2026-10-13 cumulative updates; CISA KEV

cve · CVE-2026-96951

Coverage
1
first 2026-10-14 → last 2026-10-14
Latest activity
2026-10-14
Microsoft patches an exploited Windows Shell zero-day that evades Mark of the Web protections on files and…
Peak priority
high
1 high
Targets
technology
sectors: technology
Sources cited
3
3 hosts

Action items (1)

Do-now tasks recorded on the entries about CVE-2026-96951, newest first. Check the date before acting on an older one.

  • Deploy the 2026-10-13 cumulative update for each release (KB5127648 for Windows 11 24H2, 25H2 and 26H2, KB5127646 for Windows 11 26H1, KB5126657 for Windows 10 21H2 and 22H2, KB5126655 for Server 2022, KB5126646 for Server 2025, and the others listed in the CVE record) to every Windows endpoint and server, starting with the systems whose users open mail and chat attachments or download files; Rapid7 says Windows Server 2012 receives no patch.
    2026-10-14CVE-2026-96951

Defender insights

What each entry about CVE-2026-96951 tells a defender to do, newest first.

2026-10-14HIGHexploitedMicrosoft patches an exploited Windows Shell zero-day that evades Mark of the Web protections on files and links

Exposure · triage · detection

Story timeline

  1. 2026-10-14CVE-2026-96951, Windows Shell: a Mark of the Web bypass exploited as a zero-day, fixed in the 2026-10-13 cumulative updates and listed in CISA KEV (CVSS 8.8)
    trending-vulnerabilitiesMicrosoft patches an exploited Windows Shell zero-day that evades Mark of the Web protections on files and links
ATT&CK techniques (4 across 3 tactics)

4 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessPhishing: Spearphishing Attachment · Phishing: Spearphishing Link
  • ExecutionUser Execution: Malicious File
  • Defense ImpairmentSubvert Trust Controls: Mark-of-the-Web Bypass

Initial Access TA0001

T1566.001Phishing: Spearphishing Attachment×1

Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems. Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon User Execution to gain execution. Spearphishing may also involve social engineering techniques, such as posing as a trusted source.

Evidence: 2026-10-14/cve-2026-96951-windows-shell-motw-bypass-zero-day-kev · ATT&CK page ↗

T1566.002Phishing: Spearphishing Link×1

Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems. Spearphishing with a link is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of links to download malware contained in email, instead of attaching malicious files to the email itself, to avoid defenses that may inspect email attachments. Spearphishing may also involve social engineering techniques, such as posing as a trusted source.

Evidence: 2026-10-14/cve-2026-96951-windows-shell-motw-bypass-zero-day-kev · ATT&CK page ↗

Execution TA0002

T1204.002User Execution: Malicious File×1

An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Attachment. Adversaries may use several types of files that require a user to execute them, including .doc, .pdf, .xls, .rtf, .scr, .exe, .lnk, .pif, .cpl, .reg, and .iso.

Evidence: 2026-10-14/cve-2026-96951-windows-shell-motw-bypass-zero-day-kev · ATT&CK page ↗

Defense Impairment TA0112

T1553.005Subvert Trust Controls: Mark-of-the-Web Bypass×1

Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls. In Windows, when files are downloaded from the Internet, they are tagged with a hidden NTFS Alternate Data Stream (ADS) named <code>Zone.Identifier</code> with a specific value known as the MOTW. Files that are tagged with MOTW are protected and cannot perform certain actions. For example, starting in MS Office 10, if a MS Office file has the MOTW, it will open in Protected View. Executables tagged with the MOTW will be processed by Windows Defender SmartScreen that compares files with an allowlist of well-known executables. If the file is not known/trusted, SmartScreen will prevent the execution and warn the user not to run it.

Evidence: 2026-10-14/cve-2026-96951-windows-shell-motw-bypass-zero-day-kev · ATT&CK page ↗

Entries about Windows Shell Mark of the Web security feature bypass (CVSS 8.8), exploited zero-day fixed in the 2026-10-13 cumulative updates; CISA KEV (1)

2026-10-14 · view entry permalink →

HIGHCVE-2026-96951exploitedNATOA2

CVE-2026-96951, Windows Shell: a Mark of the Web bypass exploited as a zero-day, fixed in the 2026-10-13 cumulative updates and listed in CISA KEV (CVSS 8.8)

Microsoft's 2026-10-13 release fixes CVE-2026-96951, a Windows Shell security feature bypass that Microsoft marks as exploited and not publicly disclosed (Microsoft Security Response Center, 2026-10-13); CISA added it to its Known Exploited Vulnerabilities catalog the same day, citing evidence of active exploitation (CISA, 2026-10-13). Microsoft says an attacker who exploits it could evade Mark of the Web defenses, by sending a crafted file by email or instant message or enticing the user to click a link or open an attachment (Microsoft Security Response Center, 2026-10-13). Microsoft's record gives the root cause as improper neutralization of special elements in a command (command injection, CWE-77) (Microsoft Security Response Center, 2026-10-13). Rapid7 describes the effect as Windows not showing the dialog that says it protected the PC, because the tag that triggers it is bypassed, calls this the second exploited Windows Shell zero-day this year, and says the flaw also affected Outlook.com, patched in a build several weeks ago (Rapid7, 2026-10-13). Rapid7 says Windows Server 2012 receives no patch while Server 2012 R2 does (Rapid7, 2026-10-13), and Microsoft's record lists no Windows Server 2012 product for this flaw (Microsoft Security Response Center, 2026-10-13).

Triage: a file a user created or received from a trusted local source also carries no tag; the discriminator is an internet origin (mail, chat or web download) together with the absence of the tag on the opened item.

An attacker who successfully exploited the vulnerability could evade Mark of the Web (MOTW) defenses.

Microsoft Security Response Center 2026-10-13

Once again, the immediate prize for an attacker is a Mark of the Web (MOTW) bypass.

Windows Server 2012 doesn’t receive a patch, although Server 2012 R2 does.

Rapid7 2026-10-13

Builds on: Microsoft names two exploited Windows privilege-escalation zero-days, splitting the newest and…

vulnerability14 Oct 03:39Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • cisa.gov1 (33%)
  • msrc.microsoft.com1 (33%)
  • rapid7.com1 (33%)