Microsoft Patch Tuesday July 2026: AI Finds 570 CVEs

Microsoft's July 2026 Patch Tuesday shipped 570 vulnerabilities, nearly triple the previous record of 198, after the company deployed MDASH, an AI system running more than 100 specialized agents continuously across the Windows codebase. Microsoft EVP Pavan Davuluri warned that this is not a peak but the new floor for monthly security updates, as the AI-driven pipeline compounds discoveries over time. Three zero-days were patched, including two actively exploited in the wild: CVE-2026-56155 in Active Directory Federation Services and CVE-2026-56164 in SharePoint Server.

Microsoft’s July 2026 Patch Tuesday shipped 570 vulnerabilities — nearly triple the previous record of 198, set just one month earlier in June. That number did not happen by accident. It happened because Microsoft deployed MDASH, an AI system running more than 100 specialized agents continuously across the Windows codebase. The company has already warned developers and IT teams: this is not a peak. It is the new floor for Microsoft Patch Tuesday July 2026 and every month after. What MDASH Is and Why Patch Tuesday Keeps Growing Specifically, MDASH — Microsoft’s Multi-model Agentic Scanning Harness — became public in May 2026. Rather than relying on a single model, it orchestrates 100+ specialized AI agents through a five-stage pipeline: ingest and index source code, scan for vulnerability candidates, run “debater” agents that argue for and against exploitability, deduplicate findings, and build proof-of-concept inputs to dynamically confirm each flaw is real and exploitable. Crucially, MDASH does not run on a monthly cycle. It runs continuously. Its May 2026 debut surfaced 16 CVEs, including four critical remote code execution flaws in TCP/IP, IKEv2, Netlogon, and the DNS API. July’s 570 is what happens when that pipeline compounds discoveries over months. Microsoft EVP Pavan Davuluri confirmed the trajectory directly: customers should expect “a higher volume of security updates included in each security release.” For context, Microsoft’s official Windows blog https://blogs.windows.com/windowsexperience/2026/07/09/evolving-windows-vulnerability-management-to-meet-the-speed-of-ai-powered-discovery/ frames this as moving “from a time-based patching cadence to a more continuous, risk-based approach.” The Three Zero-Days in Microsoft Patch Tuesday July 2026 Additionally, three vulnerabilities carry the zero-day designation this month. Two are actively exploited in the wild. CVE-2026-56155 is an elevation-of-privilege flaw in Active Directory Federation Services, discovered by Microsoft’s own incident response team — meaning attackers were already using it before the patch shipped. AD FS is authentication infrastructure. A foothold there is a foothold everywhere downstream. Meanwhile, CVE-2026-56164 is a SharePoint Server elevation-of-privilege flaw, and it comes with a lesson about relying on Microsoft’s severity ratings. It launched with an “exploitation less likely” label. Within days, CISA added it to the Known Exploited Vulnerabilities catalog. Security researcher Satnam Narang said it plainly: Microsoft’s exploitability index was designed for human-speed threat timelines. AI can generate a working proof-of-concept exploit for an “exploitation less likely” CVE in minutes. The rating system has not kept up. Finally, the third zero-day, CVE-2026-50661 , is a BitLocker bypass requiring physical device access. Notably, this one is publicly disclosed but not yet exploited in the wild. AI Finds Bugs for Defenders — and Builds Exploits for Attackers However, the AI advantage cuts both ways. Anthropic’s Red Team released data this month showing they generated working proof-of-concept exploits for 13 out of 14 CVEs Microsoft had rated “exploitation less likely.” The same capabilities that let MDASH find 570 bugs let attackers weaponize those bugs faster than patch deployment can follow. Time from CVE disclosure to active exploitation is collapsing across the industry. Moreover, this is not a Microsoft-specific story. Google shipped over 900 fixes in June 2026 alone. Adobe, Cisco, Mozilla, and Oracle have all accelerated patch cadence in parallel. Every organization running AI scanning is generating more patches, faster. The BleepingComputer breakdown https://www.bleepingcomputer.com/news/microsoft/microsoft-july-2026-patch-tuesday-fixes-massive-570-flaws-3-zero-days/ of July’s release captures the sheer scope: 254 elevation-of-privilege CVEs, 145 remote code execution flaws, 102 information disclosure issues — all in a single month. The CVSS 9.8 Vulnerabilities That Need Immediate Action Among the 570 patches, three reach CVSS 9.8 with “exploitation more likely” ratings. CVE-2026-55944 in Microsoft Dynamics 365 Business Central requires no authentication and no user interaction — exploit it via a crafted login request. CVE-2026-50518 and CVE-2026-56159 are Windows DHCP Server remote code execution flaws. Furthermore, July’s patch set includes nine total DHCP CVEs. According to Tenable’s full breakdown https://www.tenable.com/blog/microsofts-july-2026-patch-tuesday-addresses-569-cves-cve-2026-56155-cve-2026-56164 , DHCP infrastructure and Windows Kernel EoP flaws represent the highest-priority attack surfaces this cycle. If you run DHCP infrastructure, that is the first surface to address. How to Keep Up When Monthly Patching Can’t Consequently, reviewing 570 patches in the traditional manner is not operationally realistic. Krebs on Security https://krebsonsecurity.com/2026/07/microsoft-patches-a-record-570-security-flaws/ made the counterintuitive call to wait several days before applying this batch — at this volume, regressions from the patches themselves become a real risk, and the community catches stability issues faster than individual teams can. That calculus will only get harder as AI discovery accelerates further. Here is what actually works at this scale: Use Autopatch with hotpatch: Microsoft’s Windows Autopatch with hotpatch capability applies security updates without a reboot on eligible systems. This is the practical path to reducing disruption when monthly patch volumes consistently hit three digits. Map risk, not severity ratings: Stop triaging by Microsoft’s exploitability rating alone — the SharePoint CVE proved it is no longer reliable. Map each CVE to your exposed attack surface: internet-facing services, identity infrastructure, DHCP, SharePoint. Patch those first. Treat all Critical as immediately exploitable: AI-powered exploit generation has made “exploitation less likely” effectively meaningless as a deprioritization signal. Accelerate legacy retirement: MDASH is surfacing bugs in Windows components that have existed for decades. Those surfaces will not get cleaner — they will get more patches, indefinitely. In summary, the monthly Patch Tuesday cadence was built for a world where finding vulnerabilities required human researchers working human hours. MDASH operates at a fundamentally different speed https://www.microsoft.com/en-us/security/blog/2026/05/12/defense-at-ai-speed-microsofts-new-multi-model-agentic-security-system-tops-leading-industry-benchmark/ . The patching infrastructure needs to catch up — or the gap between discovery and deployment becomes the attack surface.