Microsoft’s September 2026 Patch Tuesday, released on 8 September 2026, was the largest monthly security release in the company’s history: roughly 964 to 974 CVEs depending on who is counting, including two Windows elevation-of-privilege flaws already exploited in the wild. If you manage Windows machines, those two zero-days, plus a handful of remotely exploitable server bugs, matter far more than the headline total. With the October release due on 13 October 2026, here is what September fixed, what went wrong afterwards and how to keep up.
Why the totals differ
Security trackers do not agree on a single number, and none of them is wrong. The difference comes down to what each one counts.
| Tracker | Total reported | What it counts |
|---|---|---|
| Tenable / Malwarebytes | 964 | CVEs customers need to act on; excludes 10 cloud-service CVEs Microsoft fixed itself |
| BleepingComputer | 966 | Microsoft CVEs in the release, excluding some third-party and cloud entries |
| CyberSecurityNews / SecurityWeek | 973–974 | Everything in Microsoft’s release notes, including cloud-service CVEs |
Severity counts differ in the same way: Tenable lists 104 critical and 860 important, while BleepingComputer counts 105 critical. Elevation of privilege made up about 45% of the fixes and remote code execution about 27%, followed by information disclosure, denial of service, security feature bypass and spoofing.
For context, July 2026 had already set a record with at least 570 fixes, according to KrebsOnSecurity, and Tenable counted 398 CVEs in the August release. September’s total was well over double August’s.
The two exploited zero-days
Both are rated Important with a CVSS score of 7.8. Neither lets an attacker break in remotely on its own, but each turns a foothold into full control of the machine.
| CVE | Component | What it does |
|---|---|---|
| CVE-2026-81963 | Windows Update Stack | A link-following flaw (improper link resolution before file access) that lets a local attacker gain SYSTEM privileges. Tenable says it is the first Windows Update Stack bug exploited as a zero-day since 2022. |
| CVE-2026-85880 | Windows Advanced Local Procedure Call (ALPC) | A heap-based buffer overflow. An attacker running code in a low-privilege AppContainer could escape the sandbox and reach SYSTEM with no user interaction. It is the second ALPC zero-day since January 2023. |
Microsoft has not said who is exploiting them. Local privilege-escalation bugs are usually chained: a phishing attachment or a browser exploit gets the attacker onto the machine as an ordinary user, and a bug like these hands them administrator-level control so they can disable security tools, dump credentials and move across the network. That is why both should be patched first, even though their CVSS scores look modest.
Other fixes worth prioritising
Tenable highlighted several flaws that Microsoft rates “Exploitation More Likely”:
- CVE-2026-69730, Windows DNS Server (CVSS 9.8, critical): an unauthenticated, remote use-after-free. Eight other DNS Server RCEs were fixed in the same release. Patch domain controllers and any DNS servers early.
- CVE-2026-69525, Remote Desktop Services (CVSS 9.8): a use-after-free in RDS. Any RDS host reachable from the internet is a priority.
- CVE-2026-69676, Windows Kerberos (CVSS 8.8, critical): an authentication bypass through capture-replay.
- CVE-2026-69380, Exchange Server (CVSS 8.1): lets a low-privileged mailbox user reach other mailboxes. Rated less likely to be exploited, but on-premises Exchange remains a favourite target.
Trend Micro’s Zero Day Initiative, quoted by SecurityWeek, counted 20 newly fixed bugs that could be wormable, meaning remote code execution with no authentication or user interaction.
The September update broke things, then got fixed
On 14 September 2026 Microsoft shipped out-of-band updates after the September patches caused Remote Desktop Services instability (failed RDP sign-ins and, in some cases, unresponsive servers), a Hyper-V folder-sharing problem with Linux VMs, and USB audio faults. The relevant KBs include KB5129195 for Windows 11 24H2 and 25H2, KB5129236 for Windows 10 21H2 and 22H2, and KB5129235, KB5129237 and KB5129238 for Windows Server 2025, 2022 and 2019. If your RDS farm misbehaved after 8 September, check that these are installed rather than rolling back the security fixes. Confirm KB numbers on Microsoft’s support pages before deploying, as BleepingComputer noted some link mismatches.
What AI has to do with it
Microsoft has been warning customers for months to expect bigger releases. In a 9 July 2026 Windows blog post, executive vice president Pavan Davuluri wrote that “the pace of vulnerability discovery is changing with advances in AI” and that users would see “a higher volume of security updates included in each security release”. An earlier MSRC note in May said both Microsoft’s own teams and outside researchers were using AI to review code more often.
It is easy to overstate the link. In a 7 October 2026 post, Microsoft said its internal AI research system had produced 52 CVEs in the September release (2 critical, 50 important) and 140 Windows CVEs between May and September. That is a meaningful slice, but most of September’s fixes came from elsewhere, including external researchers who may also be using AI tools. Tenable’s Satnam Narang put it bluntly: AI-assisted discovery “is creating larger haystacks, but it isn’t finding more needles”. The number of flaws that matter to a typical organisation each month remains small.
How IT teams should cope with bigger releases
- Prioritise by exploitation, not by count. Start with Microsoft’s “Exploitation Detected” flag, CISA’s Known Exploited Vulnerabilities catalogue and EPSS scores. In India, CERT-In’s May 2026 blueprint expects known exploited flaws on internet-facing systems to be fixed or mitigated within 12 hours where feasible; see our explainer on CERT-In’s 12-hour patch timeline.
- Use deployment rings. Push to a small pilot group on day one, a broader group after 48–72 hours, and everyone else within a week. September’s RDS breakage shows why a pilot that includes a real RDS host is worth having.
- Automate. Intune update rings, Windows Autopatch or Configuration Manager scale far better than manual approval when releases run to hundreds of CVEs.
- Shrink the blast radius. Remove local admin rights, turn on attack surface reduction rules and keep EDR active. Both September zero-days need an attacker already on the box, so these controls blunt them even before patching.
- Account for every Windows 10 machine. Only devices on supported builds or enrolled in Extended Security Updates receive these fixes. Our guide on checking Windows 10 ESU enrolment walks through it.
A quick checklist for home and small-office users
- Open Settings > Windows Update, select Check for updates, install everything and restart.
- Check again after restarting until it says you are up to date.
- If Remote Desktop or USB audio stopped working after early September, install the latest optional or out-of-band update rather than uninstalling security patches.
FAQ
Is 964 or 974 the correct number? Both. The difference is about 10 cloud-service CVEs that Microsoft fixed on its own side and which need no action from you.
When is the next Patch Tuesday? Tuesday 13 October 2026. Expect another large release and check whether it adds new exploited flaws before you plan your rollout.
Last reviewed: 9 October 2026.
Sources
- Microsoft Security Response Center: Security Update Guide
- Microsoft Security blog: 3 lessons from frontier AI vulnerability research (7 October 2026)
- Tenable: September 2026 Patch Tuesday addresses 964 CVEs
- SecurityWeek: Microsoft patches record 974 vulnerabilities
- BleepingComputer: Emergency Windows updates fix RDS failures
- KrebsOnSecurity: Microsoft patches a record 570 security flaws (July 2026)

Leave a Reply