Microsoft shipped fixes for 570 security vulnerabilities on July 14, its largest Patch Tuesday ever and nearly triple the record set just one month earlier. Two of the three zero day flaws in the batch were already being exploited before a patch existed.
The company says the jump comes from its own artificial intelligence tools finding bugs faster than human researchers ever could, exactly the kind of proactive defense Microsoft has spent the year building toward. That same success is why security teams are now buried under more fixes than most can realistically test in a month.
A Record 570 Fixes, Three of Them Zero Days
The release breaks down into 254 elevation of privilege (EoP) flaws, 145 remote code execution (RCE) bugs, 102 information disclosure issues, 35 denial of service flaws, 17 security feature bypasses and 16 spoofing vulnerabilities, a category split reported consistently by BleepingComputer and the security firm Qualys. Fifty nine carry Microsoft’s Critical rating, and 48 of those 59 are remote code execution bugs, the kind that let an attacker run code on a victim’s machine with little help from the target.
Add up those category counts and you get 569, one short of the headline number, a small reminder of how messy these tallies have become this year.
Three of the fixes are zero days, meaning they were known before Microsoft had a patch ready. Two were already being used in real attacks. CVE-2026-56155 is an EoP flaw in Active Directory Federation Services (AD FS), the system that signs employees into corporate networks and connected apps, and it lets an already authenticated attacker climb to administrator rights. CVE-2026-56164 is a SharePoint Server bug that needs no password at all; an outsider can reach it over the network and grab elevated access directly. The third, CVE-2026-50661, is a Windows BitLocker bypass that requires physical access to a device and was publicly disclosed but not confirmed as exploited at release time.
Not every tracker agrees on how big the release actually was.
| Tracker | CVE Count | What It Covers |
|---|---|---|
| BleepingComputer, Qualys, Automox | 570 | Microsoft’s core monthly bundle, excluding Chromium, Edge and fixes issued earlier in the month |
| Tenable | 569 | Nearly identical count, with one advisory categorized differently |
| Zero Day Initiative, SecurityWeek, Malwarebytes | 621 to 622 | A broader tally that folds in additional product variants and bundled advisories |
| Google (separate Chromium and Edge release) | 468 | Shipped the same week but excluded from Microsoft’s own count entirely |
Whichever number you use, the release obliterated June’s high mark, which several trackers put at roughly 200 CVEs, or Common Vulnerabilities and Exposures, the industry’s standard catalog of flaws.
Why Did Microsoft’s Bug Count Suddenly Triple?
Microsoft says artificial intelligence is doing the finding. An internal system called the Multi-Model Agentic Scanning Harness, or MDASH, runs several AI models against the Windows codebase around the clock, and Microsoft warned customers days before the release that counts would keep climbing before they level off.
Pavan Davuluri, a Microsoft executive vice president, wrote in a July 9 blog post that customers should expect a higher volume of security updates as AI speeds up discovery. Microsoft first detailed the multi-model agentic scanning system behind that shift back in May. It runs a two stage pipeline: a scanning pass that flags candidate bugs in critical binaries, then a validation pass that uses model to model debate to strip out false positives before an engineer ever sees the finding.
Trey Ford is chief strategy and trust officer at Bugcrowd, a crowdsourced security testing platform. He put the shift in dollar terms rather than code terms. “AI has collapsed the cost of finding vulnerabilities, and this increase in volume is a new floor, not the ceiling,” he said, adding that the pattern would hold “at least for a while.”
Mayuresh Dani, a security research manager at Qualys, said the surge was expected well before it arrived. “What we’re observing is that AI automated fuzzing, LLM-assisted variant hunting, and static analysis at scale are discovering bugs faster than enterprises can remediate,” he said.
Not everyone agrees on how long that will last. Microsoft has told customers the acceleration is not a blip. The vulnerability intelligence firm VulnCheck is less certain, noting that AI-assisted bug hunting is reshaping disclosure volumes across the industry, but that it is still unclear whether counts keep rising once the easy bugs are cleared out or whether newer models simply keep finding more.
SharePoint and AD FS Are Already Under Attack
The Cybersecurity and Infrastructure Security Agency, known as CISA, added both exploited flaws to its Known Exploited Vulnerabilities catalog within hours of the release. Federal agencies have until July 17 to patch the SharePoint bug and until July 28 for the AD FS flaw, short deadlines that signal active targeting of identity and collaboration systems.
- CVE-2026-56164 lets an unauthenticated attacker reach SharePoint Server over the network and elevate privileges, with no user interaction required.
- CVE-2026-56155 lets an already authenticated attacker on an AD FS server escalate straight to administrator level access.
- Credit for the finds goes to Microsoft’s own Detection and Response Team for the AD FS bug, and to researchers with Mandiant Incident Response and Google Cloud’s FLARE OTF team, plus an anonymous researcher, for the SharePoint flaw.
- A stopgap exists for SharePoint: turning on the Antimalware Scan Interface, or AMSI, and setting Request Body Scan to Full until the patch is fully rolled out.
What is not yet known matters just as much.
- Microsoft has not said exactly how either flaw was used in attacks, or for how long attackers had access before detection.
- No public count exists of how many organizations were compromised before the patch shipped on July 14.
- Neither flaw’s severity score fully matches how it is being used in the wild, a gap researchers flagged the same day.
That last point is not a small quibble. Microsoft rates the AD FS bug at 7.8, and analysts at the patch management firm Automox called that number a trap. “The score understates it,” they wrote, since it sits well below other bugs in the release even though it is the one already being exploited. The SharePoint bug fares worse on paper: Microsoft rates it just 5.3, in the Moderate band, even as its own exploitability assessment lists it as detected in active use, the kind of mismatch Automox said “most triage queues will bury.”
Microsoft Isn’t Alone in the Flood
Google, Adobe, Cisco and Mozilla have all sped up their own release schedules this year, and the AI-hunting phenomenon reaches well beyond Redmond.
- 468 Chromium and Edge fixes shipped from Google the same week, separate from Microsoft’s own count and excluded from its Patch Tuesday tally.
- 10,000-plus vulnerabilities have been surfaced by roughly 50 partners in AI-assisted audits across the industry, according to the AI company Anthropic’s own account of its Project Glasswing initiative.
- 2,000 bugs found at Cloudflare alone using Anthropic’s unreleased Claude Mythos Preview model, 400 of them rated high or critical severity.
- A 170 percent jump in published CVEs hit the Apache Software Foundation, which Anthropic separately backed with a 1.5 million dollar donation to help maintainers keep pace.
Adobe announced this month it is moving from one security bulletin a month to two, saying a once-a-month release window is “no longer fast enough to stay ahead of our adversaries.” Chris Goettl, a vulnerability management expert at the IT software firm Ivanti, noted that Cisco, Mozilla and Oracle are all shipping updates more often this year too, and that Google’s patch batches in June alone totaled more than 900 fixes.
Patching Becomes a Fixed Cost, Not a Fire Drill
Tenable researchers have projected that Microsoft could address more than 3,000 vulnerabilities across all of 2026 if the current pace holds, based on the firm’s own tracking of this year’s releases.
Qualys, responding to the July release, urged three concrete changes for security teams trying to keep up.
- Prioritize by exploit likelihood, not just severity: shift from CVSS-only rankings toward the Exploit Prediction Scoring System (EPSS) plus CISA’s Known Exploited Vulnerabilities list, patching anything scoring above 0.5 on EPSS within 24 to 36 hours.
- Shrink the attack surface: keep AD FS off the open internet, block public access to on-premises SharePoint, and make sure remote management tools cannot be reached from anywhere.
- Build a validation pipeline: test updates on a small group of systems with automated rollback ready before pushing approved patches to the full fleet.
Trey Ford framed the response in budget terms rather than technical ones. “Leadership teams need to stop treating patch volume as a monthly surprise,” he said. “We must fund it as a fixed operating cost, because the intake will not be going back down for a while.” He added that the organizations that come out ahead will not be the fastest patchers this month, but the ones whose process can keep scaling as intake keeps climbing.
AI vendors are making a similar bet on the funding side. Anthropic has committed 100 million dollars in model usage credits to its Project Glasswing partners, a sign the AI-versus-AI race in vulnerability hunting is expected to run for years, not months.
Today, July 14, 2026, marks a pivotal moment in our industry. We are officially moving past the traditional ‘Patch Tuesday’ approach and entering an era of continuous, high-volume security updates.
That statement came from researchers at Nightwing, a cybersecurity firm, issued the same day as the release. Microsoft’s next scheduled Patch Tuesday lands August 11, giving defenders roughly four weeks to work through this month’s list before the counter resets.
Frequently Asked Questions
How Many Vulnerabilities Did Microsoft Patch in July 2026?
Microsoft’s own count for the day was 570, though trackers using a broader methodology that includes more product variants put the figure at 622. Under that broader count, Windows alone accounted for 416 of the vulnerabilities, followed by 82 each in Office and Office 2016, 46 in Microsoft Edge, and 17 in SharePoint Server.
What Is MDASH?
MDASH is short for Microsoft Security’s Multi-Model Agentic Scanning Harness, the internal system that runs several AI models against Windows binaries to flag and validate potential flaws before engineers review them. Microsoft has said the tool found 16 of the bugs fixed in May’s Patch Tuesday release entirely on its own, though the company has not broken out an exact figure for how many of July’s fixes came from the same pipeline.
Which Vulnerabilities Should I Patch First?
Install fixes for the two actively exploited flaws immediately, CVE-2026-56155 in AD FS and CVE-2026-56164 in SharePoint Server, ahead of everything else on the list. Windows 11 users can find the relevant cumulative update under KB5101650 or KB5099414 depending on their build, while the BitLocker bypass can generally wait unless a device carries sensitive data and travels outside a secured office.
Is the BitLocker Bug a Real Risk for Home Users?
CVE-2026-50661 only matters if someone else gets physical hold of your device, so most desktop users at home face little practical risk. It is also not an isolated case. Researchers have tied it to a run of BitLocker bypasses this year that included flaws nicknamed bitskrieg and YellowKey, making it the third such disclosure in 2026.
Has SharePoint Been a Target Before?
Yes. SharePoint Server has drawn repeated attacker attention since the ToolShell exploit chain tore through unpatched, internet-facing servers in 2025, and CISA had already flagged fresh SharePoint exploitation twice earlier in 2026 before this month’s bug. Security teams treat any new SharePoint zero day as high priority for that history alone.
When Is Microsoft’s Next Patch Tuesday?
Microsoft’s next scheduled release lands August 11, 2026. Some researchers had theorized that odd-numbered months historically run lighter than even ones, a pattern July’s record-breaking, odd-month release just broke.
