What happened
May’s Microsoft Patch Tuesday addressed more than 137 security vulnerabilities, bringing the company’s total for the first five months of 2026 to over 500 patched flaws, putting it on pace to break its own annual record. April’s release addressed 173 vulnerabilities. Tom Gallagher, vice president of engineering at Microsoft’s Security Response Center, acknowledged that AI tools are driving the surge and said the company expects patch releases to continue trending larger.
Alongside Tuesday’s release, Microsoft disclosed a new internal AI system codenamed MDASH that it has been using to hunt for security flaws in its own software. MDASH found 16 of the vulnerabilities patched this month, including four rated critical, without any human researcher identifying them first. In a validation test run backwards through five years of previously confirmed flaws in two Windows components, MDASH independently rediscovered 96% of known flaws in one component and 100% in the other.
Among this month’s highest-priority vulnerabilities are two rated 9.8 out of 10: CVE-2026-41089 in Windows Netlogon, which can be triggered by a specially crafted network request to a domain controller and may allow unauthenticated remote code execution, and CVE-2026-41096 in the Windows DNS Client, which in certain unspecified configurations could also allow unauthenticated remote code execution. A third critical vulnerability rated 9.9, CVE-2026-42898, affects on-premises Microsoft Dynamics 365 installations and allows an authorized attacker to execute code over a network through improper control of code generation.
The broader AI-driven patch wave is visible beyond Microsoft. Apple addressed 52 vulnerabilities in its most recent update, Google shipped 127 Chrome security fixes on the same day, and Oracle announced a shift from quarterly to monthly patching for critical issues. Google’s Threat Intelligence Group separately reported what it described as the first known case of a threat actor using an AI-developed zero-day exploit in a planned mass exploitation campaign, which Google said it disrupted before the attack launched.
Who is affected
All organizations running Windows Server with domain controller configurations, Windows DNS Client, and on-premises Microsoft Dynamics 365 installations face direct exposure from the three highest-severity vulnerabilities. The broader patch volume affects every organization running Microsoft products, which across enterprise environments means virtually every major organization globally.
Why CISOs should care
The MDASH disclosure marks a meaningful shift in how Microsoft is approaching vulnerability discovery internally, and the retrospective recall results are credible validation of the approach. Sixteen AI-discovered vulnerabilities in a single month’s patch release, including four critical ones, is not a pilot result. It is a production outcome.
More broadly, the convergence of AI-assisted discovery across Microsoft, Anthropic’s Project Glasswing, Google’s threat intelligence work, and independent researchers using similar tools is producing the patch wave that the NCSC warned about last month. Copy Fail, Dirty Frag, and now five months of record Microsoft patch volumes are early illustrations of what Gallagher described as the increasing pace and breadth of vulnerability discovery across the software industry. Organizations whose patching and exposure management practices were built for a slower-moving environment face a structural challenge that is not going to slow down.
3 practical actions
- Prioritize patching CVE-2026-41089 and CVE-2026-41096 immediately across all Windows Server and DNS Client deployments: Both are rated 9.8, both allow unauthenticated remote code execution, and the Netlogon vulnerability specifically targets domain controllers, making it a direct path to domain compromise. Treat these as emergency patches rather than standard monthly remediation.
- Assess on-premises Dynamics 365 exposure for CVE-2026-42898 and apply patches before granting any new authorized network access: The 9.9 CVSS rating reflects the severity of code execution via improper code generation control. Organizations running on-premises Dynamics 365 should patch immediately and audit authorized user access to the affected systems.
- Evaluate whether your current patching velocity and exposure management processes are calibrated for the new patch volume reality: Microsoft, Apple, Google, and Oracle are all increasing their patch release frequency and volume in response to AI-assisted discovery. If your patching cadence was designed around monthly cycles with manageable volume, assess whether you need to shift toward continuous vulnerability management with prioritization tooling that can handle higher throughput.
John Kevin Hao is a news and feature writer covering cybersecurity, technology, and business targeted for professional audiences.