Microsoft fixed a record number of flaws on October 13, 2026, and only one of them is confirmed exploited. If you read one line: install the October Windows updates now, and treat CVE-2026-96951, a Windows Shell bypass of Mark of the Web, as the urgent one. The rest of the release is large, but the exploited and critical items fit on a short list.
This post summarizes BleepingComputer's Patch Tuesday report and separates what that report states from what we could not check. We did not install the updates or test any exploit, and we did not open Microsoft's own advisory pages while writing this, so use Microsoft's Security Update Guide for exact builds and KB numbers.
TL;DR
| Question | Answer |
|---|---|
| How big was the release? | About 1,411 flaws, called a record (other outlets say 1,413) |
| Is anything exploited? | Yes: CVE-2026-96951, a Windows Shell Mark-of-the-Web bypass |
| Other zero-days? | Two publicly disclosed, not exploited: CVE-2026-108398 and CVE-2026-92707 |
| Critical count? | 70 rated Critical: 57 remote code execution, 11 elevation of privilege, 2 spoofing |
| Do I need to act today? | Yes: install the October Windows updates, then work down the list below |
| Does anything affect AI agents? | One Critical bug is in Azure SRE Agent (CVE-2026-69435, elevation of privilege) |
What happened on October 13
Microsoft's monthly security release on October 13 covered Windows, Office, Azure services, .NET and Microsoft's Linux-based components. BleepingComputer counts 1,411 flaws, and says the figure excludes 348 flaws Microsoft fixed earlier in October in Azure, Mariner, Exchange Server and other products. Its own category breakdown is labelled approximate and totals 1,389:
| Category | Count (approximate) |
|---|---|
| Elevation of privilege | 677 |
| Remote code execution | 317 |
| Information disclosure | 254 |
| Denial of service | 73 |
| Security feature bypass | 40 |
| Spoofing | 28 |
Other outlets report 1,413 CVEs, and one counts 1,771. The differences come from what each outlet includes, such as the earlier fixes and third-party components Microsoft lists in the same table. The practical answer does not change: it is a very large release, and the number to watch is the handful of exploited and Critical items, not the total.
The three zero-days
Microsoft calls a bug a zero-day when it is exploited or public before a fix exists. October has three.
| CVE | Product | Status | What it does |
|---|---|---|---|
| CVE-2026-96951 | Windows Shell | Exploited | Command injection that lets an unauthorized attacker bypass a security feature over a network, specifically Mark of the Web |
| CVE-2026-108398 | .NET Framework | Publicly disclosed | An untrusted search path that lets an authenticated local attacker bypass Windows Defender Application Control and run code inside a protected process; found by James Forshaw of Google Project Zero |
| CVE-2026-92707 | MessagePack-CSharp | Publicly disclosed | Improperly controlled memory allocation that allows a remote, unauthenticated denial of service |
Why the Mark of the Web bypass matters
Windows tags files that came from the internet with Mark of the Web. That tag is what makes SmartScreen warn you and what makes Office open a downloaded document in Protected View. A bypass removes the tag's effect, so a malicious file or archive opens without the warnings that normally stop careless clicks. It does not run code by itself, which is why attackers pair this kind of bug with a phishing file or a booby-trapped download.
BleepingComputer says Microsoft shared no details on how the bug was exploited or who reported it. That means there is no public list of indicators to hunt for yet; patching is the defence.
CISA and the federal deadline
Security Affairs and SOC Prime report that CISA added CVE-2026-96951 to its Known Exploited Vulnerabilities catalog on October 13, giving federal civilian agencies until October 16 to patch. BleepingComputer does not mention CISA, and we have not checked the catalog entry ourselves, so confirm it there. If your organization follows KEV deadlines, that date has already passed.
The Critical list worth reading
BleepingComputer counts 70 Critical flaws: 57 remote code execution, 11 elevation of privilege and 2 spoofing. It lists these Microsoft-product items by name:
- CVE-2026-70229: Windows Active Directory Domain Services, remote code execution
- CVE-2026-96222 and CVE-2026-108131: AD FS, spoofing
- CVE-2026-77900: Azure App Service, remote code execution
- CVE-2026-83943: Azure API Center, information disclosure
- CVE-2026-83947: Azure Event Grid, spoofing
- CVE-2026-69435: Azure SRE Agent, elevation of privilege
- CVE-2026-62840: Linux kernel, elevation of privilege (in Microsoft's Mariner distribution)
The report does not give CVSS scores for these, and its listing of Mariner items is truncated, so the full Critical set is longer than this. The Azure entries are cloud services, so check Microsoft's advisory for whether you need to act; the Windows, AD FS and Active Directory items are on machines you run.
What to install, in order
- Windows Update on every Windows machine, servers and laptops, to pick up CVE-2026-96951. Restart as your update policy requires.
- Domain controllers and AD FS servers, for CVE-2026-70229, CVE-2026-96222 and CVE-2026-108131. These sit in the middle of your authentication, so patch them in a maintenance window soon, not eventually.
- Developer and build machines with .NET Framework, for CVE-2026-108398. It needs local access and an authenticated user, so it ranks below the exploited bug but matters where Windows Defender Application Control is your control.
- Apps that use MessagePack-CSharp, for CVE-2026-92707. This is a library fix, so update the package and redeploy rather than relying on Windows Update.
- Check your Windows edition. BleepingComputer reports that Windows 11 24H2 Home and Pro and Windows 10 Enterprise LTSB 2016 reached the end of updates with this release, and Windows 11 23H2 Enterprise, Education and IoT Enterprise stop receiving security updates next month. Machines on those editions will not get future fixes.
Other vendors patched the same week
BleepingComputer's roundup lists October advisories from Adobe, Atlassian, Cisco, Citrix, Dell, Docker, Fortinet, GitLab, Ivanti, SAP and SonicWall, and says several had flaws exploited in the wild, including Citrix CVE-2026-88779, Fortinet CVE-2026-104286 and an Ivanti Connect Secure zero-day. If you run any of those, check their advisories this week too. For GitLab specifically, see our write-up of the CVSS 10.0 self-managed GitLab flaw.
What this means if you run AI agents
Most of this release is ordinary Windows hygiene, but two points touch agent work.
First, Mark of the Web is part of how Windows decides whether a downloaded file deserves a warning. If an agent or a script on a Windows machine downloads files, archives or installers, a bypass in that layer means one less safety net, so keep those machines patched like any other endpoint.
Second, one Critical item is in Azure SRE Agent (CVE-2026-69435, elevation of privilege). We have no details beyond its listing, so we cannot say how it could be abused. If your team uses that service, read Microsoft's advisory for it directly.
Beam does not patch Windows and is not an endpoint protection product. What it covers is the agent layer: it watches what coding agents such as Claude Code and Codex run, flags risky actions like credential exposure, and can deny some through hooks. A patched operating system and a watched agent are separate controls, and you need both. For the rest of the month's patches and incidents, see our October 2026 attacks timeline.
What we could and could not verify
| Claim | Status |
|---|---|
| About 1,411 flaws fixed, called a record | Reported by BleepingComputer; other outlets say 1,413 or more; category totals do not add up |
| CVE-2026-96951 is exploited | Reported by BleepingComputer from Microsoft's release; details not shared |
| CISA added it to KEV on Oct 13 with an Oct 16 deadline | Reported by Security Affairs and SOC Prime; not in BleepingComputer; not checked in the catalog |
| 70 Critical flaws | Reported by BleepingComputer |
| Windows 11 24H2 Home and Pro reached end of updates | Reported by BleepingComputer; not checked against Microsoft's lifecycle page |
| Which Critical bugs attackers will use | Not known |
We have not read Microsoft's own release notes or CVE pages for this release. Treat counts as the reporters' figures and check the Security Update Guide for your exact KB.
Frequently asked questions
How many vulnerabilities did Microsoft fix in October 2026?
BleepingComputer counts 1,411 flaws, calling it a record. Other outlets report 1,413, and the category totals in BleepingComputer's own breakdown add up to 1,389, so treat the exact number as approximate.
Which October 2026 Patch Tuesday bug is being exploited?
CVE-2026-96951, a Windows Shell security feature bypass that lets an attacker get around Mark of the Web. Microsoft has not said how attackers used it or who reported it.
What is Mark of the Web and why does a bypass matter?
Mark of the Web is a tag Windows puts on files that came from the internet, so SmartScreen and Office can warn you before they run or open. A bypass lets a malicious download skip those warnings, which makes phishing files and archives more likely to succeed.
Did CISA add the Windows Shell bug to its exploited list?
Security Affairs and SOC Prime report that CISA added CVE-2026-96951 to its Known Exploited Vulnerabilities catalog on October 13 with a federal deadline of October 16. BleepingComputer does not mention CISA, so check the catalog yourself.
Are the other two zero-days being exploited?
Microsoft lists CVE-2026-108398 (a .NET Framework bypass of Windows Defender Application Control) and CVE-2026-92707 (a MessagePack-CSharp denial of service) as publicly disclosed, not exploited, at the time of the release.
Do I need to do anything if I run Windows 11 24H2 Home or Pro?
BleepingComputer reports that Windows 11 24H2 Home and Pro, and Windows 10 Enterprise LTSB 2016, reached end of updates with this release. Check your edition against Microsoft's lifecycle page and plan an upgrade.
Related reading
- October 2026 attacks timeline
- October 2026 software supply chain incidents tracker
- GitLab CVE-2026-110264: CVSS 10.0 unauthenticated RCE
- Brotli CVE-2026-111497: affected software and detection
- Apple iOS 27.2 fixes 163 vulnerabilities
- PHP2Shell patch guide for Ubuntu, Debian, RHEL and Docker
Details are accurate as of October 29, 2026, based on BleepingComputer's October 13 report and the secondary sources linked above. Counts and CVE details can change as Microsoft updates its advisories.