OFFSEC · Offensive Security

Microsoft’s largest Patch Tuesday has five counts, one exploited flaw and a triage experiment

October's release is the first above 1,000 CVEs, but analysts do not agree on the number. Microsoft's new risk cohorts help with exposure questions, and the one exploited bug may sit outside them.

Microsoft’s October update is the first monthly release above 1,000 CVEs. The exact size depends on who is counting. Tenable reports 1,407 [5]. CrowdStrike, SecurityWeek and Cybernews report 1,413 [6][7][11]. The Zero Day Initiative and Security Affairs report 1,415 [4][8]. Microsoft’s own risk cohort table adds up to 1,118, which at least one outlet published as the total [1][10]. The spread is not a scandal. It does show that, at this volume, a vulnerability team’s first job is to decide what it is counting. Only one of those CVEs has confirmed exploitation.

The counting problem

ZDI’s Dustin Childs says counting this load is tricky and does not explain the method further. He notes that the release includes a MessagePack-CSharp bug issued by a third party [4]. September shows the same pattern. Computerworld gives 963 CVEs, IT-Connect 973 and Cybernews 999 [12][9][11]. Severity counts differ too: CrowdStrike lists 75 critical, Tenable 69 and Cybernews 78 [6][5][11].

The differences most likely come from what is in scope: third-party components, cloud CVEs fixed server-side, Extended Security Update channels and late additions. CrowdStrike notes six cloud-service CVEs that need no customer action [6]. None of the analyses publishes its inclusion rules in full. For an operator, the practical consequence is simple. A scanner’s count, a vendor blog’s count and an internal ticket count will not match, and reconciling them by hand is wasted effort.

The one that is exploited

CVE-2026-96951 is a Windows Shell security feature bypass rated 8.8. Microsoft says it is exploited in the wild [5][6]. It allows a crafted file, sent by email or instant message, to evade Mark of the Web protections, which means the warnings and restrictions applied to downloaded content. A user still has to act on the file [5][7]. Tenable says it is the third Windows Shell flaw exploited in the wild in 2026 [5]. SecurityWeek reports that Microsoft credits Fujitsu, Anthropic and an independent researcher, and that no details of the attacks have been shared [7].

The CVE record, published by Microsoft as CNA on 13 October, describes the root cause as command injection in Windows Shell [2]. CISA’s KEV feed lists it as added on 13 October, due 16 October [3]. The CISA enrichment in the same record still shows an SSVC entry timestamped 8 October with exploitation marked as none, beside the KEV addition [2]. Treat the KEV listing as current.

The three-day deadline is not unusual this month. The KEV feed gives the same three-day window to the Ivanti Connect Secure flaw added the same day and to five older CVEs added on 8 October [3].

Two other flaws were publicly disclosed before release. CVE-2026-108398 bypasses Windows Defender Application Control enforcement in .NET Framework; Microsoft considers exploitation unlikely. CVE-2026-92707 is a denial-of-service flaw in MessagePack-CSharp [6][7].

Risk cohorts

Alongside the release, the Microsoft Security Response Center published what it calls provisional risk cohorts. It defines a cohort as a group of CVEs that require a similar customer assessment, even where they share no root cause or CVSS score [1]. The 15 example cohorts range from 24 CVEs in directory, federation and certificate infrastructure to 136 in Windows filesystems, storage and backup. Each poses one question, such as whether lower-privileged code can run on a host, or which machines act as RDP clients, gateways or servers [1].

Microsoft is careful about scope. The cohorts are not official vulnerability categories, do not change update guidance, do not replace per-CVE assessment and are not shown in the Security Update Guide. Microsoft makes no commitment to publish them every month and asks for feedback at CVE@microsoft.com [1]. The page also has small internal inconsistencies: its remote-access example cites 64 CVEs where the table lists 65, and its Office example cites 119 where the table lists 135 [1]. Its one reference to AI is that AI-assisted research may make this kind of approach more useful [1].

The gap is coverage. IT-Connect reports that 289 CVEs fall into no cohort, including the exploited Shell flaw, all Exchange Server CVEs and most SharePoint and SQL Server CVEs [9]. Microsoft’s page does not state that figure. The arithmetic between its 1,118 table total and a 1,407 release is consistent with it, if no CVE sits in two cohorts [1][9]. A team that worked only from the cohorts would have started with neither the exploited bug nor the internet-facing server products.

ZDI welcomes the idea, comparing it to the old security bulletin groupings, and doubts enterprises will use it well [4].

What the volume does and does not mean

Elevation of privilege accounts for 677 CVEs, about 48 per cent, followed by remote code execution at 317 and information disclosure at 254 [6]. CrowdStrike counts 23 Office CVEs exploitable through the preview pane and five critical Outlook remote code execution flaws [6]. ZDI counts 59 that meet its wormable definition [4]. SecurityWeek reports that Microsoft has patched more flaws this month than in all of 2025, with its 2026 total above 4,000 [7].

The exploitation rate has not moved with it. ZDI counts 15 Microsoft zero-days so far in 2026, against 17 at the same point in 2023 [4]. Its reading is that AI shortens the time to find existing bugs, on both sides, without creating them, and that discovery is outpacing exploitation [4]. Security Affairs and SecurityWeek also attribute the surge to AI-assisted discovery [7][8].

What to do

  • Patch CVE-2026-96951 first on every Windows endpoint, and do not rely on Mark of the Web warnings as a control until it is deployed [3][5].
  • Next, take the server products the cohorts do not cover: SharePoint CVE-2026-102866, unauthenticated and the only critical SharePoint bug, and Exchange CVE-2026-70571 [4][9].
  • Prioritise AD DS CVE-2026-70229 and the AD FS spoofing flaws on identity infrastructure [5][6].
  • Disable the Outlook and Explorer preview pane where Office patching will lag, given the 23 preview-pane CVEs [6].
  • Use the cohort questions to scope exposure, then check each cohort’s exclusions before closing a ticket [1][9].
  • Fix the counting rule once: decide whether third-party, cloud-fixed and ESU CVEs are in scope, and stop reconciling external totals [4][6].
  • Do not neglect Adobe: ZDI rates the ColdFusion bulletin APSB26-144, with a CVSS 10 pre-authentication bug, as the most urgent of the month [4].

The offensive security reading

Volume favours the side that chooses. An attacker needs one reliable bug on a reachable surface, and this month the confirmed one is a user-assisted bypass that removes a warning prompt [5][7]. Defenders cannot answer 1,400 CVEs one by one, and Microsoft’s cohorts concede as much. The cohorts are useful as exposure questions. They are not a priority list, and the exploited bug may not be in them. Red teams should test whether a MotW bypass changes their initial access success. Blue teams should keep two lists: what is exploited, and what is reachable. Everything else waits.

Sources

Every R3KONX article cites its primary material. 12 sources, in order of first citation. Links open the original publication.

  1. Using risk cohorts to prioritize security updates Microsoft Security Response Center · 2026-10-13
  2. CVE-2026-96951 (CVE record, CNA Microsoft, with CISA ADP container) CVE Program (cvelistV5) · 2026-10-14
  3. Known Exploited Vulnerabilities catalog (JSON feed, catalog version 2026.10.13) CISA via GitHub (cisagov/kev-data) · 2026-10-13
  4. The October 2026 Security Update Review Zero Day Initiative (Trend Micro) · 2026-10-13
  5. Microsoft's October 2026 Patch Tuesday addresses 1,407 CVEs (CVE-2026-96951) Tenable · 2026-10-13
  6. October 2026 Patch Tuesday: Updates and Analysis CrowdStrike · 2026-10-13
  7. Microsoft Patches Record 1,413 Vulnerabilities, Including Exploited Windows Zero-Day SecurityWeek · 2026-10-14
  8. Microsoft Patch Tuesday sets new record with 1,415 CVEs in October 2026 updates Security Affairs · 2026-10-14
  9. Patch Tuesday: Microsoft tests risk cohorts to help prioritize 1,400 CVEs IT-Connect · 2026-10-14
  10. Microsoft Fixes 1,118 Vulnerabilities in October Patch Tuesday and Introduces New Risk Cohorts Cyber Security News · 2026-10-13
  11. Microsoft Patch Tuesday fixes record 1,400 flaws, one zero-day Cybernews · 2026-10-14
  12. Microsoft's Patch Tuesday updates: Keeping up with the latest fixes Computerworld · 2026-09-14

Researched and written by the R3KONX analysis desk from the cited primary material. Microsoft's Security Update Guide and the cohort PDF could not be retrieved; CVE details come from the CVE record, CISA's KEV feed and the cited vendor analyses. The statement that 289 CVEs fall outside the cohorts is IT-Connect's analysis and is not stated by Microsoft. Corrections to event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.