Skip to main content
All incident reports
Incident report

Microsoft patches record 1,413 flaws, including exploited Windows Shell zero-day

Microsoft's 13 October updates fixed a record 1,413 vulnerabilities, one of which attackers are already exploiting to get files past Windows Mark of the Web warnings. Two days later the company shipped more than 30 further fixes, most of them for Office.

· First published

The short version

  • The patch batch. Microsoft released updates for 1,413 vulnerabilities on 13 October 2026, its largest monthly release and more than it fixed in all of 2025. One flaw in the batch is being exploited in the wild.
  • The exploited flaw. CVE-2026-96951 lets an attacker evade Mark of the Web, the tag Windows puts on downloaded files so security features treat them cautiously. Microsoft says it has been exploited; CISA added it to its Known Exploited Vulnerabilities catalogue on the same day.
  • Publicly disclosed bugs. Two other patched flaws were public before fixes shipped: a .NET Framework bug that bypasses Windows Defender Application Control, and a denial-of-service flaw in MessagePack-CSharp.
  • Follow-on Office fixes. On 15 October Microsoft issued more than 30 further patches, most for Office and two dozen of them remote code execution flaws. Microsoft says none of the newly resolved issues has been exploited.
  • Volume and triage. Microsoft credits large language models with the surge in bug discovery, and has now fixed more than 4,000 CVEs in 2026. Researchers advise triaging by proven exploitation rather than by CVE count.

Timeline

DateEvent
13 OctMicrosoft releases October updates fixing 1,413 vulnerabilities, including an exploited Windows Shell flaw, and introduces risk cohorts for prioritisation.
13 OctCISA adds CVE-2026-96951 to its Known Exploited Vulnerabilities catalogue.
15 OctMicrosoft issues more than 30 further fixes, most of them for Office; it says none has been exploited.

The exploited zero-day

It also says that in an email or instant message attack an attacker could send a crafted file, and that the attacker would have to convince the recipient to take action, such as opening it or following a link.

The sources classify the bug slightly differently. Microsoft's advisory and SecurityWeek call it a security feature bypass; The Hacker News lists it as a command injection flaw that bypasses a security feature over a network. Microsoft credits Fujitsu researchers Riku Bamba and Yuya Chudo, Anthropic's Benoit Sevens and a researcher named yhw with reporting it. No source says who is exploiting the flaw or whom they targeted.

The record patch load

The 13 October release covered 1,102 flaws in Windows, 134 in Office, 61 in developer tools, 36 in SharePoint Server and 22 in SQL Server. More than 670 allow privilege escalation, over 300 remote code execution and 250 information disclosure. The Hacker News says more than 70 are rated critical; Krebs on Security puts the figure at 78. Microsoft has now fixed past 4,000 CVEs in 2026.

Microsoft credits large language models with the rise in bug discovery, and researchers agree that AI-assisted hunting has sped up finding on both sides. Dustin Childs of the Zero Day Initiative said: "Hundreds of CVEs in a single release used to be the exception; now it's the baseline." Krebs reports that the volume puts strain on corporate teams that must test updates before rolling them out.

Microsoft introduced risk cohorts, groups of CVEs that call for a similar customer assessment, to help teams prioritise, while saying they are a starting point rather than a final decision. Tyler Reguly of Fortra noted that 26 Microsoft vulnerabilities have appeared in CISA's KEV catalogue in 2026 and said teams should patch those first. He said: "Security leaders should focus on exploitable risk, and ask whether their teams have the clarity, capacity and support to act."

Publicly disclosed flaws and follow-on fixes

Two patched flaws had been disclosed publicly before fixes shipped. CVE-2026-108398, found by Google Project Zero's James Forshaw, lets an attacker with existing local access load a crafted .NET assembly and bypass Windows Defender Application Control (WDAC); Microsoft judged exploitation unlikely. CVE-2026-92707 is a denial-of-service bug in MessagePack-CSharp, used in Visual Studio and .NET, which Microsoft has not assessed. Patches also cover CVE-2026-21413, a heap overflow in the Raw Image Extension rated 9.8 out of 10, triggered when Windows renders a thumbnail of a crafted RAW image.

On 15 October Microsoft issued more than 30 further fixes, most of them for Office, including two dozen remote code execution flaws, six of which can be triggered through the Preview Pane. Word took most of the patches, with a few for Excel, Outlook, PowerPoint and SharePoint. Microsoft says none of the newly resolved issues has been exploited. It also updated October advisories to add fixes for Office LTSC for Mac 2021 and 2024 and Office 365 for Mac.

What is not known yet

  • Who is exploiting CVE-2026-96951, and which organisations or sectors have been targeted.
  • How many systems or organisations the exploitation Microsoft reports has affected.
  • Whether the exploited flaw was used to deliver a particular malware family, and what attackers did after evading Mark of the Web.
  • Whether CVE-2026-108398 has been used in attacks, beyond Microsoft's view that exploitation is unlikely.
  • Whether every supported Windows 10 build receives these fixes, given that Microsoft has extended free updates to October 2027.

What to do

If you run Windows or Microsoft server products

  1. Apply the October updates, starting with CVE-2026-96951.
  2. Prioritise the Microsoft flaws listed in CISA's Known Exploited Vulnerabilities catalogue over the rest of the 1,413.
  3. Use Microsoft's risk cohorts as a starting point, then check each CVE for active exploitation, severity and attack vector before deciding.
  4. Confirm which Windows 10 devices still receive updates; Microsoft has extended free updates for them to October 2027.

If you use Office or .NET

  1. Install the 15 October Office fixes, including the two dozen remote code execution patches; six can be triggered through the Preview Pane.
  2. Patch .NET Framework for CVE-2026-108398 even though Microsoft considers exploitation unlikely, because it lets an attacker with existing local access bypass endpoint restrictions.
  3. Test updates before estate-wide deployment, given the size of the batch.

For everyone else

  1. Do not rely on Mark of the Web warnings alone: the exploited flaw exists to suppress them.
  2. Treat unexpected attachments and links in email or instant messages as hostile, since the attacker needs the recipient to open the file.
  3. Plan for patch volumes of this size as the norm, and set priorities by proven exploitation rather than by the number of fixes.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.