Microsoft's Patch Tuesday Is Breaking Records Because AI Found the Bugs

Microsoft's June Patch Tuesday was a record-breaker. Nearly 200 CVEs across Windows OS and supported software, nearly three dozen rated "critical," and exploit code for at least three of those weaknesses already sitting on GitHub. But the headline isn't just the numbers — it's what Microsoft and the security community are saying about why the numbers are climbing.

\n\n

Microsoft's engineers and the wider security community are increasingly leaning on AI tools to find bugs. "Some surveys put AI usage among security professionals generally at 90%, so it's unsurprising that this volume of patches may become the norm," said Satnam Narang, a senior research engineer at Tenable. Pandora's proverbial box is open: as better models get better at pattern-matching through massive codebases, the yield of discovered vulnerabilities goes up. That means more patches, more maintenance windows, and more sysadmins refreshing Windows Update on a Tuesday morning they'd rather spend on anything else.

\n\n

What makes this June cycle especially interesting is the human side of the story. The researcher known as Nightmare Eclipse — who claims to be a former Microsoft employee — has been dropping zero-day exploits for Windows flaws, including one dubbed "GreenPlasma" that targets the Windows Collaborative Translation Framework. Immediately after Microsoft released today's patches, the researcher published an exploit for what they claimed was a zero-day in Windows Defender. Meanwhile, Microsoft received blowback last month after announcing it might pursue legal action against researchers who disclose bugs, though they clarified that they'd only act if the law was broken. Nightmare Eclipse has pledged an even bigger "bone shattering" drop for July 14. The real story here isn't that Patch Tuesday got bigger — it's that AI is making it inevitable. If 200 CVEs in a single month is the new normal, the question for IT teams isn't whether they can keep up, but whether they can afford not to.

Krebs on SecuritySource article image
Source image 2
dius: 8px;" />
Source image 1
\n

Sources

\n

• A Record-Breaking Patch Tuesday for June 2026 — Krebs on Security

\n

• Windows 11 KB5094126 & KB5093998 cumulative updates released — BleepingComputer

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more