Microsoft just shipped the largest Patch Tuesday in history. The interesting question isn't how many bugs were fixed — it's who, or what, found them.
Microsoft's June Patch Tuesday lands with roughly 200 vulnerabilities — counts range from 198 to 208 depending on who's doing the arithmetic — comfortably demolishing the previous record of around 170 CVEs set in October 2025. Thirty-three are rated Critical, twenty-eight of those remote code execution, and three zero-days were publicly disclosed before patches existed. The one mercy: nothing is confirmed exploited in the wild. Yet.
And that's before the asterisk. Microsoft separately addressed 360 Edge/Chromium vulnerabilities this month — an order of magnitude above the historical norm — to the point where Redmond has simply stopped enumerating Chromium CVEs in its Security Update Guide. When a vendor gives up counting, you know the curve has changed shape.
Every CVE in this cycle requires customer action. If your patch process was designed for a 60-CVE month, June is the month it meets reality.
Buried in the advisory for CVE-2026-49160 — the HTTP/2 denial-of-service zero-day — is a detail that will be remembered long after the patch itself: Microsoft credits the discovery to OpenAI's Codex. It is the first publicly confirmed case of an AI system directly reporting a vulnerability that made it into a Patch Tuesday advisory.
It didn't come from nowhere. February 2026 saw the first attribution of CVEs to AI discovery tools; April brought Project Glasswing and a visible spike in the curve; last month Microsoft's own VP of Engineering, Tom Gallagher, warned that releases at this scale could become the new normal as AI accelerates vulnerability discovery beyond anything previously seen.
The uncomfortable symmetry: the same frontier models doing the finding are also collapsing the time it takes to weaponise what's found. Analysts now openly cite Claude Mythos, GPT 5.5 and DeepSeek v4 as the engines turning N-day vulnerabilities into working exploits faster than most organisations can complete a patch cycle. The window between "patched" and "exploited" used to be measured in weeks. Plan for days.
Two hundred CVEs is a triage problem, not a reading list. The short list, in order of "stop what you're doing":
Cumulative updates: KB5094126 (Windows 11), KB5094127 (Windows 10). Adobe, for its part, shipped 123 fixes across 11 advisories — 47 critical. Everyone's having a big month.
Also folded into this cycle: a Visual Studio Code zero-day allowing attackers to steal GitHub tokens with a single click. Microsoft was forced into a stopgap fix on 3 June after a researcher published working exploitation instructions — the polite term for "the patch schedule was chosen for them".
If your developers' tokens were exposed in the disclosure window, rotate them. Tokens are credentials; treat the disclosure window as a breach window until proven otherwise.
The prediction making the rounds — and we think it's right — is that 100+ CVE months are now the minimum, with surveys putting AI usage among security professionals at around 90%. Pandora's box doesn't have a close animation.
The strategic read: a record month is a capacity problem dressed as a security problem. The rate of discovery has decoupled from the rate at which patches can be tested and deployed, and that gap is exactly where AI-assisted exploitation lives. If your remediation cadence is still monthly, the question is no longer whether to change it — it's whether the monthly model is fit for purpose at all.
One more clock ticking: the Secure Boot certificate deadline is 17 days out. This was the last Patch Tuesday before it. Consider yourself briefed.