A record-breaking patch release — nearly triple last month’s count — signals a structural shift in how vulnerabilities are discovered, and how quickly they can be exploited.
Summary
- Microsoft patched at least 570 security flaws in July 2026, almost triple the previous month’s record-setting release, with AI-assisted discovery cited as the primary driver of higher volumes.
- Three zero-days are actively being exploited in the wild, including two elevation-of-privilege vulnerabilities affecting Active Directory Federation Services and SharePoint.
- A BitLocker security feature bypass (CVE-2026-50661) and a Microsoft Copilot remote code execution flaw (CVSS 9.6) are among the high-priority items requiring immediate attention.
- Microsoft’s exploitability index is under scrutiny after research showed AI models can produce working exploits for vulnerabilities rated ‘Exploitation Less Likely’ or ‘Exploitation Unlikely.’
- Adobe, Cisco, Mozilla, Oracle and Google are all increasing patch cadence, meaning security teams face a sustained uplift in patch management workload across the board.
A patch count that changes the baseline
Microsoft’s July 2026 Patch Tuesday addressed at least 570 security vulnerabilities across Windows and related software — nearly three times the volume from the previous month, which itself had set a record. Close to 60 of those vulnerabilities carry a critical severity rating, meaning an attacker could seize remote control of an affected device with minimal or no user interaction. Microsoft attributed the surge directly to artificial intelligence accelerating the pace at which vulnerabilities are identified across its codebase.
Three zero-days already in use
Security teams should treat three vulnerabilities as immediate priorities: two elevation-of-privilege flaws that are confirmed as actively exploited in the wild. The first, CVE-2026-56155, is an Active Directory Federation Services bug; the second, CVE-2026-56164, affects Microsoft SharePoint. Both allow an attacker to escalate their privileges on a compromised Windows system. A third item deserving attention is CVE-2026-50661, a BitLocker security feature bypass. Microsoft says this flaw requires physical access to a device and is not yet being actively exploited, but details have been made public — raising the risk profile considerably.
Copilot flaw adds an AI-specific attack surface
Jack Bicer, director of vulnerability research at Action1, flagged CVE-2026-48561, a remote code execution vulnerability in Microsoft Copilot carrying a CVSS score of 9.6. According to Microsoft, an unauthenticated attacker could exploit this flaw by hosting a malicious website that causes Microsoft Edge for Android to automatically send crafted prompts to Copilot when a user visits the site. This represents an emerging class of risk: AI-integrated products creating novel attack paths that traditional threat models may not yet account for.
The exploitability index may no longer be fit for purpose
The SharePoint zero-day illustrates a growing problem with how the industry assesses exploitability. Microsoft originally rated CVE-2026-56164 as ‘exploitation less likely,’ yet it was added to CISA’s Known Exploited Vulnerabilities catalogue on 1 July. Satnam Narang, senior staff research engineer at Tenable, pointed to research from Anthropic’s red team in which its AI model produced proof-of-concept exploits for 13 of 14 vulnerabilities rated ‘Exploitation Less Likely’ or ‘Exploitation Unlikely.’ As Narang put it, this means ‘our way of looking at Patch Tuesday has changed, because the exploitability index is centered around humans, not AI tools.’ For security teams relying on that index to triage patching, the risk calculus has quietly shifted.
An industry-wide acceleration
This is not a Microsoft-specific phenomenon. Adobe announced on the same day it is moving to twice-monthly security bulletins, also citing AI as a factor in the decision. Cisco, Mozilla and Oracle are shipping updates more frequently. Google’s patch output in June 2026 exceeded 900 fixes in a single month. Chris Goettl at Ivanti observed this convergence directly: major software vendors are collectively increasing their patch cadence, and security operations teams need to plan accordingly. Patch management programmes designed around a monthly rhythm are under pressure.
Stability risks with large releases
With a release of this size, there is an elevated probability that some patches introduce system stability issues. Security professionals advising enterprise environments should factor in testing time before broad deployment. For end-user environments where patching decisions are more discretionary, waiting a few days to observe any reported stability problems is a reasonable precaution, balanced against the active exploitation of the zero-day vulnerabilities.
Why it matters
For CISOs, this release is a signal of a structural change rather than a one-off event. AI is simultaneously compressing the timeline for vulnerability discovery and exploit development, which means the window between a patch being issued and a working exploit appearing in the wild is narrowing. The failure of Microsoft’s own exploitability ratings to anticipate active exploitation of the SharePoint zero-day demonstrates that historical risk-triage frameworks need to be revisited. With elevation-of-privilege vulnerabilities accounting for roughly 250 of this month’s fixes — and Active Directory and SharePoint both represented in the zero-day list — organisations running on-premises Microsoft infrastructure face meaningful exposure. The Copilot RCE flaw also signals that AI-integrated tooling introduces attack surfaces that require their own assessment methodology. Finally, with every major software vendor increasing patch frequency, security teams should expect sustained pressure on patch management capacity and budget.
What to do now
- Prioritise patching CVE-2026-56155 (Active Directory Federation Services) and CVE-2026-56164 (SharePoint), both confirmed as actively exploited in the wild.
- Assess exposure to CVE-2026-48561 (Microsoft Copilot RCE, CVSS 9.6), particularly in environments where Microsoft Edge for Android is deployed.
- Review physical access controls for devices where CVE-2026-50661 (BitLocker bypass) is relevant, given that technical details are already public.
- Back up Windows systems and data before applying this month’s updates, given the elevated risk of stability issues associated with a release of this scale.
- Consider a staged rollout with a short hold period in non-critical environments to identify stability issues before broad deployment.
- Revisit your patch-triage methodology: given evidence that AI tools can generate exploits for vulnerabilities rated ‘less likely’ to be exploited, the exploitability index alone should not drive prioritisation decisions.
- Review patch management capacity planning in light of increasing release cadence from Microsoft, Adobe, Cisco, Mozilla, Oracle and Google.
