Microsoft shipped 966 fixes because AI is hunting its code

Microsoft's September 2026 Patch Tuesday fixed 966 flaws — the largest single security release the company has ever published. Two are under active exploitation. Before you panic about the number, understand where it came from: Microsoft pointed an AI vulnerability discovery system at its own source code, and the machine is finding bugs faster than humans ever did. The supply of CVEs went up. Your actual risk did not move nearly as much.

What actually happened

BleepingComputer's count is 966, with 105 rated Critical — 81 of those remote code execution. SecurityWeek puts it at 974; the gap is in what each tally includes. Either way it dwarfs July's 570, which Krebs on Security called a record at the time, and August's roughly 400. The breakdown skews heavily toward elevation of privilege — 438 of them — with 258 RCE and 173 information disclosure.

The two exploited zero-days are both local privilege escalation to SYSTEM:

• CVE-2026-85880 — a heap buffer overflow in Windows Advanced Local Procedure Call, reported by Volexity and Proofpoint researchers
• CVE-2026-81963 — link-following in the Windows Update Stack, credited to Romain Deperne and Microsoft Threat Intelligence Centre

Neither is remotely reachable. An attacker needs code execution on the box first.

Separately, Microsoft published 204 cloud-service fixes earlier this month covering Azure AI Language, Copilot Studio, Entra ID, Power Automate, Fabric and Cosmos DB — all already mitigated on Microsoft's side, no customer action possible.

Why a record Patch Tuesday matters for your business

The honest read: the denominator changed, not the threat. A fuzzer that never sleeps will keep producing four-digit months. If you treat every Patch Tuesday as a fire drill scaled to the headline count, you will burn out by Christmas and still miss the two that matter.

What we'd actually do with this month:

Patch the two exploited CVEs on anything a person logs into. Both are post-compromise steps — they turn a foothold into a domain problem. That means your real control is upstream: phishing-resistant MFA, no local admin for daily accounts, and knowing which machines run unmanaged software. If an attacker never gets that first shell, an ALPC heap overflow is a footnote.

For the other 964, keep your normal ring cadence. Pilot group, then broad. Nothing in the volume justifies skipping a test ring, and a rushed deploy of 900-plus fixes is its own outage risk.

The cloud batch is the part worth sitting with. Nine of those CVEs carried CVSS scores of 9.8 to 10.0 in services like Copilot Studio and Azure AI Language, and you could not have patched, detected or audited any of them. Your AI automation layer is now in the CVE feed, and your only lever is vendor choice. Ask what a provider commits to disclosing and how fast — most standard terms promise nothing.

Sources: BleepingComputer, SecurityWeek, Krebs on Security.