Bar chart of Microsoft monthly security update vulnerability counts from April to September 2026, rising from 164 to a record 974
Fig. 1 — Microsoft's monthly security update volume, April through September 2026 (sources: Microsoft advisories, KrebsOnSecurity, Corvus Cybersecurity)

1. Why this release is being called the biggest ever

On September 8, 2026, Microsoft shipped the largest monthly security update in its history: 974 vulnerabilities. That number is not steady accumulation. It is the peak of a steep, bumpy climb: 164 in April, 120 in May, 200 in June, 570 in July, 398 in August, and 974 in September. September alone came in at 2.4 times August and nearly six times April, pushing Microsoft's fiscal 2026 total past 2,600.

What is inside those 974 matters as much as the total. 113 were rated "Critical," 438 were privilege-escalation flaws, and 258 were remote code execution (RCE) bugs. In a real attack chain these overlap almost every time: RCE gets a foothold, privilege escalation reaches the domain controller, lateral movement carries the attacker to backups and file servers. A team that patches only the RCE items is not secure at this volume.

Tenable senior staff research engineer Satnam Narang puts privilege escalation at roughly 46% of all vulnerabilities disclosed in 2026, with September at 41%, close to that long-run average. That is not a one-month artifact; it is the settled new normal.

As for why the numbers jumped, Microsoft gave warning in July: it has been using AI tooling to find zero-days in bulk, and faster discovery produces faster patch output. The explanation holds up technically, but it creates a new problem — discovery speed has outrun the speed at which humans patch. That is why CISA retired its weekly vulnerability bulletin in September and moved to risk-based prioritization under BOD 26-04, issued in June, which requires the highest-risk flaws to be closed within three days, followed by a full forensic triage to confirm the system was not already compromised.

Four-stage attack chain: remote code execution, privilege escalation, lateral movement and domain takeover, ending at file servers, backup systems and the domain controller
Fig. 2 — The four stages of a real attack chain. The first two dominate this batch; the last two decide how far an attacker gets
Stacked bar of the 974 CVEs: 438 elevation-of-privilege, 258 remote code execution, 155 other and 2 zero-days, of which 113 were rated Critical
Fig. 3 — What the 974 are made of. Only two are zero-days, and both are already being exploited

2. The two zero-days that need patching today

Two vulnerabilities here were actively exploited by real attackers before the patch shipped — the hardest prioritization signal there is.

CVEComponentTypeMicrosoft ratingWhy it is dangerous
CVE-2026-85880Windows ALPC (Advanced Local Procedure Call)Heap buffer overflow, local privilege escalationSeverity score 7.8An attacker holding a low-privilege local account can escalate to SYSTEM
CVE-2026-81963Windows Update stackImproper link resolution, local privilege escalationImportantAbuses a flaw in the update mechanism itself to escalate

One detail is easy to miss: both actively exploited flaws are rated below Critical — one at 7.8, the other merely Important. A team that sorts by CVSS and works downward would schedule these behind the 113 Critical items while attackers are already using them. This is the classic failure mode in vulnerability management: the score describes theoretical severity; exploitation status describes actual threat. They are separate dimensions and both have to be read.

Two Critical flaws also deserve explicit mention:

Other fixes worth noting: CVE-2026-62878 (DNS Server RCE), CVE-2026-62893 (Deployment Services RCE) and CVE-2026-58231 (Commerce Cloud / NetWeaver). On September 17 Microsoft also shipped an out-of-band fix for Azure AI Foundry (CVE-2026-85889, CVSS 10.0, unauthenticated privilege escalation), though cloud flaws of that class are remediated on Microsoft's backend and need no customer action.

3. What a 20-person IT team should do with 974 patches

This is the practical problem. A 20-person team cannot triage, test and roll out 974 patches in a few weeks. "Patch everything next month" is already too slow — CISA's three-day deadline does not bind companies outside the US federal government, but the two exploited flaws will not wait for your schedule either.

Our recommendation is to split the work into four tiers instead of one long to-do list:

TierTriggerThis batchTesting bar and deadline
Tier 1 · EmergencyActively exploited (in CISA KEV or confirmed by the vendor)CVE-2026-85880, CVE-2026-81963Test on representative machines, deploy the same day, done in 3 days
Tier 2 · ExposurePre-auth RCE, or running on internet-reachable systemsCVE-2026-69730 (DNS), CVE-2026-69829 (Shell)Map the exposure first, then sequence; within 1 week
Tier 3 · Core assetsCritical flaws on domain controllers, certificate services, identity infrastructureThe identity and directory-service subset of the 113 Criticals2 weeks, scheduled separately
Tier 4 · RoutineEverything elseRoughly 900Normal monthly maintenance window

The step that collapses the workload is narrowing the asset list before ranking patches. 974 CVEs sounds overwhelming, but the components actually running in your environment are typically a few dozen. Walk the estate once and record which components are in use, which machines they sit on, and which of those are internet-reachable. What is left needing immediate action is usually a dozen items, not a thousand.

The second thing to build is a re-triage trigger. A vulnerability nobody exploits today can enter the KEV catalog next week; CVE-2026-33824 is the textbook case, patched four months before it was listed as exploited. So triage is a standing rule, not a one-time sort: when KEV adds a CVE your environment contains, it jumps to Tier 1. Automate a daily KEV diff — it takes minutes and is the highest-return habit here.

One counter-intuitive reminder: patching is not the same as being secure. Fortra security research director Tyler Reguly notes that compatibility testing before deployment is labor-intensive and often eats after-hours time. If you test all 974 before shipping any, the two exploited flaws sit open for the entire test cycle. Patch what is being exploited, then run the full regression. Reverse that order and you have inverted the priority.

Four-tier priority queue pyramid: from Tier 1 Emergency (exploited, within 3 days) to Tier 4 Routine (about 900, normal maintenance window)
Fig. 4 — The four-tier queue. The criteria are exploitation and exposure, not score

4. A minimum viable approach for small businesses

If you have no dedicated security staff, collapse the four tiers into three steps:

  1. This week, patch the two zero-days (CVE-2026-85880, CVE-2026-81963). No need to take the company offline at once: validate on a domain controller, an internet-facing service and an ordinary office endpoint, then roll out fleet-wide. These two are the only ones in this batch that invite a direct hit if left open.
  2. Immediately inventory any Windows Server 2012 or 2016 machines you still run. If they expose DNS or Remote Desktop, CVE-2026-69730 is an open gap. The right fix for these old systems is usually not patching — many are out of support — but planning replacement or isolating them at the network layer.
  3. Make a daily KEV check routine. No tools required. A script, or someone spending five minutes each morning on the KEV list, beats buying another scanner. This is the highest-leverage step in the process.

If you already have ransomware protection or backup requirements, our ransomware incident response order covers the next step. A fully patched machine that has already been compromised needs a completely different response sequence.

All figures here come from Microsoft's September 2026 security update announcements, the CISA Known Exploited Vulnerabilities catalog, and reporting from KrebsOnSecurity and SecurityWeek. Every CVE identifier, score and date can be traced back to those sources. Our contribution is translating technical advisories into an executable action list; patch selection and applicability still have to be judged against Microsoft's official documentation, because every environment differs.

A three-step playbook for a 20-person IT team: patch the two zero-days this week, inventory legacy servers now, run a daily KEV diff
Fig. 5 — The three-step playbook for a 20-person IT team. None of it needs an extra budget