July 2026 Patch Tuesday: Record 622 CVEs, 2 Zero-Days

Microsoft shipped the largest single-month security release in its history on July 14, 2026, fixing a record 622 vulnerabilities across its product line — and two of them were already being exploited in the wild as zero-days before a patch existed. The sheer volume, roughly triple a typical Patch Tuesday, has a specific cause that Microsoft has now acknowledged: the company is using AI to hunt bugs faster than ever, and defenders are seeing the results land all at once.

The headline numbers

By the count from SecurityWeek, Microsoft’s July release addresses 622 CVEs, making it the company’s biggest Patch Tuesday on record. Other trackers logged slightly different totals — Tenable and Security Boulevard cited 569 CVEs, Rapid7 and BleepingComputer counted around 570, and Security Affairs put the figure at 621 — a spread that reflects how vendors scope Microsoft-issued versus third-party and republished CVEs. However it is tallied, the release is unprecedented in size, and Windows accounts for the overwhelming majority of the fixes.

Three of the flaws are zero-days — vulnerabilities that were public or under attack before a patch was available. Two were actively exploited in the wild; the third was publicly disclosed but not yet weaponized. For defenders, that trio, not the raw 622, is where the urgency sits.

The two exploited zero-days

CVE-2026-56164 — Microsoft SharePoint Server. The flaw drawing the most attention is a vulnerability in on-premises SharePoint caused by missing authentication for a critical function. Microsoft has confirmed in-the-wild exploitation, and the attack profile is the dangerous kind: an attacker who can reach the SharePoint server can act over the network with no existing privileges and no user interaction, at low attack complexity. Descriptions of the bug’s effect vary between elevation of privilege and spoofing across trackers, but the practical risk is consistent — an unauthenticated, remotely reachable weakness in a platform that sits close to an organization’s identity and file infrastructure. It affects SharePoint Server 2019, SharePoint Server Subscription Edition, and SharePoint Server 2016. Microsoft notes that its Antimalware Scan Interface (AMSI) integration can help detect malicious POST requests, but given active exploitation, patching is the priority, not a mitigation to lean on.

CVE-2026-56155 — Active Directory Federation Services (AD FS). The second exploited zero-day is an elevation-of-privilege flaw in AD FS stemming from insufficient granularity of access control, letting an authorized attacker elevate privileges locally. Microsoft credited the discovery to Jeremy Kingston and Scott Clark of its Detection and Response Team (DART) — a detail that strongly suggests the bug was uncovered while investigating real intrusions, not in the abstract. AD FS sits at the heart of federated single sign-on for many enterprises, which makes any privilege-escalation path through it a high-value target.

The third zero-day, CVE-2026-50661, is a BitLocker security-feature-bypass (CVSS 6.1) that was publicly disclosed before a patch but requires physical access to the target device — a materially lower risk than the two network-reachable, actively exploited flaws above.

Why the count exploded: AI-driven bug hunting

The record size is not an accident of scheduling. Microsoft has confirmed it is using AI to accelerate internal discovery of software vulnerabilities, describing a multi-model agentic scanning harness (MDASH) that identifies flaws faster than human review alone. The company has warned customers plainly: they should expect a higher volume of security updates in each release as a direct result.

That shift reframes what a “big” Patch Tuesday signifies. Historically, a spike in fixes could hint at a surge in attacker activity or a newly analyzed product area. Increasingly, it reflects the defender’s own tooling finding more bugs internally before adversaries do — a genuinely positive dynamic, but one that transfers the burden downstream to the administrators who now have to test and deploy far more updates each month. AI is compressing the discovery half of the vulnerability lifecycle; the patching half still runs at human speed.

What to prioritize

With 622 fixes, triage is the whole game. The two actively exploited, network-reachable flaws come first:

1. Patch SharePoint (CVE-2026-56164) on every on-premises server in the farm. As with prior SharePoint fixes, applying the update is necessary but not always sufficient — administrators should confirm the fix is fully applied across the farm and treat internet-adjacent servers as the top priority. On-premises SharePoint has been a repeat target; this is the latest entry in a long run of SharePoint remote-code-execution and privilege flaws under active attack.
2. Patch AD FS (CVE-2026-56155) on federation servers, given its role in single sign-on and the DART attribution that points to real-world exploitation.
3. Work through the remaining critical Windows CVEs on a normal risk-ranked schedule, and address the BitLocker bypass where physical-access threats are part of the model.

The broader defensive posture matters as much as the individual patches. Network-reachable, no-interaction flaws are exactly the class that automated exploitation weaponizes at scale once a technique circulates, so zero-trust segmentation that limits lateral movement remains a critical backstop for the window between disclosure and full deployment. And as AI accelerates vulnerability discovery on both sides of the fence — including in the AI tooling stack itself and in Microsoft’s own security products — the gap between “patch available” and “patch applied” is where risk now concentrates.

What it means

The July 2026 Patch Tuesday is a milestone in two directions at once. It is the largest Microsoft has ever shipped, and it is an early, concrete look at what security operations become when AI is doing the bug-finding.

The signal in the number. A 622-CVE release is not, on its own, evidence that Microsoft’s software got dramatically less secure overnight. Microsoft’s own account — that MDASH and agentic scanning are surfacing more flaws internally — suggests the opposite: more bugs are being caught before attackers reach them. The cost is operational load. Security teams that budget for a typical monthly cadence now face releases several times larger, and the org that patches slowly is the one that gets hurt.

Who is exposed. Organizations running on-premises SharePoint and AD FS are in the immediate blast radius. Both are common, both are internet-adjacent or identity-critical, and both now have exploited-in-the-wild zero-days with a patch available. The classic patch-gap dynamic applies — the fix is out, and the laggards become the targets.

What to watch next. Expect broader scanning and opportunistic exploitation of CVE-2026-56164 now that it is public and confirmed active, and watch whether the AI-driven discovery trend makes oversized Patch Tuesdays the new normal. If Microsoft’s warning holds, the strategic question for every IT organization is no longer whether it can absorb a busy patch month, but whether its deployment pipeline can keep pace with a discovery engine that no longer runs at human speed. The number to track is not 622 — it is how fast the exposed servers actually get patched.