Microsoft fixed a record 1,411 security flaws in October. A year ago it averaged about 100 a month, Krebs on Security reports, so by our own division the October load was roughly 14 times heavier.

That pace is the explanation officials are floating for a bad week in US systems. Microsoft 365 was down for almost 24 hours, the FAA grounded flights nationwide, Chase’s online banking failed and an NSA classified network went offline. Sen. Mark Warner, vice chair of the Senate intelligence committee, says AI is exposing flaws so fast that companies and agencies are forced to patch everything at once. Director of National Intelligence Jay Clayton blamed patching for the NSA outage.

The organizations involved offer four different causes. Of the four, only the NSA outage has a sitting official naming patching as the cause, and the NSA’s own statement says scheduled maintenance.

Microsoft security fixes a month: about 100 a year ago versus a record 1,411 in October 2026, about 14 times as many by our sum
Microsoft’s October fix count was about 14 times its monthly average a year ago, by our own sum.

In this piece:

Six days, four outages

Six days, four outages

The run began on Thursday, November 12 and ended on Tuesday, November 17. On paper each outage has its own cause. They landed close enough together that people started asking whether one thing connected them.

Timeline of four US outages: Microsoft 365 November 12, FAA ground stop November 13, Chase banking November 16, NSA network November 17
Four outages in six days: Microsoft, the FAA, Chase and the NSA.
DateWhoWhat happenedHow longCause as stated
Nov 12 to 13Microsoft 365Email, Teams and Copilot down23 hours 50 minutesA latent defect in a July fix, a Teams failover and lost capacity
Nov 13FAANationwide ground stopAbout 3:30 p.m. to 8:15 p.m. ETLegacy equipment flooded with connection attempts after a router change
Nov 16ChaseCustomers had trouble reaching their accountsBack to normal that evening“A software bug in on-premise hardware systems”
Nov 17AppleApple Pay, iCloud and apps disruptedWorking normally by early evening“An internal update”
Nov 17NSAClassified network NSANet degradedNot statedScheduled routine maintenance (the NSA); patching after a PHP flaw (Clayton)
Causes are as each organization or official stated them. Sources are listed at the end.

Cybersecurity journalist Nicole Perlroth listed the same four in a post on X on November 17. “We need far more analysis of why so much is breaking at once,” she wrote. Her thread goes on to make claims about attacker speed and tooling that we haven’t verified, so we don’t repeat them here.

Nicole Perlroth on X, November 17, 2026. Her thread makes further claims we haven’t verified.

Two days later the Associated Press put the same question in a headline: “Tech outages are piling up, and AI is raising the stakes. Could this be the new normal?”

Inaccessible email inboxes. Banking delays. And a communications meltdown that grounded airplanes for hours, followed by waves of other travel disruptions. In an increasingly interconnected world, some fear such disruptions could be the new normal.

— The Associated Press (@apnews.com) 2026-11-19T11:30:13Z
The Associated Press on Bluesky, November 19, 2026.

Microsoft: a July fix and a failover

Microsoft’s preliminary report puts the outage at 4:20 p.m. UTC on November 12 to 4:10 p.m. UTC on November 13, or 23 hours and 50 minutes. The BBC reported it reached at least 70 countries and that more than 430 million people use the affected products.

The report names three factors. The first is a defect in a fix that had been rolling out to the gateway servers behind Microsoft 365 since July. It went unnoticed for more than three months. Microsoft says its load testing missed it because the tests “tended to focus on weaker hardware with fewer cores,” and the problem is worse on newer machines.

The second is a Teams failover about 15 hours earlier, which sent more traffic to the gateway that also carries Exchange Online. The third is that nearly 14% of the gateway’s server capacity was already out of service for an unrelated reason. Together they tipped it over. Traffic from failed servers moved to healthy ones, which hit the same bug, and at the lowest point more than 80% of the servers were unresponsive.

Microsoft 365 outage chain: a bug hidden in a July fix, more load with 14% less capacity, then over 80% of gateway servers down
A defect that sat quiet for three months knocked out most of the gateway servers.

The fix was slow because the defect was months old. Microsoft says its usual rollback and feature-flag tools couldn’t quickly revert it, and its automated recovery wasn’t built to restore service from that state. Engineers wrote an update that returned the code to its previous state, then took servers out of service in groups, applied it and restarted them, sometimes more than half a region at a time. Teams, OneDrive and SharePoint could move off the faulty gateways sooner. Exchange Online couldn’t, for scale reasons, so email was down longest.

Microsoft’s November 13 statement called it “a technical issue not related to cyber or AI / agents.” A bad update is the kind of failure Warner and Clayton describe, but Microsoft doesn’t link this one to the AI-driven patch surge.

The Associated Press on the outage: “Microsoft outage hits companies and governments worldwide.”

The FAA: a flood of connection attempts

Air route traffic controllers at work at the Washington air route traffic control center, an FAA file photo
Air route traffic controllers at the Washington center. FAA file photo, public domain, not from the outage.

The FAA ordered the ground stop at about 3:30 p.m. ET on November 13 and said traffic resumed at 8:15 p.m. Transportation Secretary Sean Duffy said in a social media post that it followed “a communication issue impacting all Air Route Traffic Control Centers.” Homeland Security Secretary Markwayne Mullin told reporters: “It’s just a telecommunications outage as of now. This isn’t another 9/11. I cannot repeat that enough.”

FAA command center advisory 111 of November 13, 2026, headed National Ground Stop, saying all airports are ground stopped until further notice
The FAA command center’s advisory: “ALL AIRPORTS ARE GROUND STOPPED.” FAA, public domain, via Wikimedia Commons.
White House video, November 13: “Secretary Mullin & Secretary Duffy provide an update on the FAA National Ground Stop.” Public domain, via Wikimedia Commons.
Audio only: Duffy at the White House briefing on November 13, a little over seven minutes. Public domain, via Wikimedia Commons.

The FAA’s own account came two days later. It says legacy equipment became unstable when data began flooding its network at a rate of 1,000 connection attempts every four to five seconds. Instability hit 17 of its 22 air route traffic control centers. L3Harris had deployed a new router at El Dorado, Arkansas, which Aviation Week reported was a Juniper unit replacing an older Cisco one. The FAA has paused installs of that router. HPE, which owns Juniper, said the device “functioned as it was configured to by the installer.” The FAA hasn’t established a root cause.

El Dorado, Arkansas, where the FAA says the new router was deployed. Map © OpenStreetMap contributors.

AI came up on the FAA side too. The agency recently expanded a new AI air traffic tool called SMART, and its vendor, Air Space Intelligence, said its software didn’t cause the ground stop, NBC News reported. Administrator Bryan Bedford said there was zero evidence of anything nefarious or AI-related.

Operators canceled about 12,462 flights, though not all trace directly to the ground stop. Bernstein estimated the pretax hit to American, Delta, United and Southwest at $345 million.

12,462

flights canceled by operators, including 9,082 by major airlines

17 of 22

air route traffic control centers hit by instability

$345M

Bernstein estimate of the pretax hit to four big airlines

FAA ground stop November 13: 17 of 22 control centers unstable, 12,462 flights canceled, $345 million estimated airline hit
The ground stop canceled about 12,462 flights and cost four big airlines an estimated $345 million.
Travellers stand under four departures boards at New York’s JFK airport during the FAA ground stop on November 13, 2026
Passengers under the departures boards at New York’s JFK during the ground stop, November 13. Photo: Sashimi-b, CC BY-SA 4.0, via Wikimedia Commons.

Travellers and pilots followed it as it happened. A thread on Reddit’s r/aviation went up as the stop was ordered, and a North Carolina station posted the all-clear on TikTok that night. Both are embedded as their authors posted them; we haven’t checked what the comments claim.

A thread on Reddit’s r/aviation: “US FAA declares national ground stop.”
WRAL News on TikTok: “11/13/26: FAA lifts nationwide ground stop.”
CNN: “FAA orders nationwide ground stop due to ‘extraordinary circumstances’,” from November 13, before the FAA gave its explanation.

Chase, Apple and the NSA

Chase said its November 16 disruption came from “a temporary issue related to a software bug in on-premise hardware systems.” Customers at other banks and Zelle users were affected too, and normal operations returned that evening.

Apple said on November 17 that “an internal update caused some outages this morning” across its services, including Apple Pay and iCloud. By early evening all systems were working normally, according to its status page.

The NSA called its November 17 outage “temporary degradation during scheduled routine maintenance” and said mission-critical capabilities stayed fully operational. Clayton went further on Fox Business, saying patching after a PHP vulnerability “has caused some of these systems to not come back up when you patch them as expected. That is what has happened at the NSA today.” He said institutions are “taking their systems down” to install fixes, and that officials see no sign of a coordinated cyberattack or state-sponsored activity.

Jay Clayton in a blue suit, in front of the US flag and an official seal

Some systems have to hand off to other systems, and those handoffs are not coming as expected.

Jay Clayton, Director of National Intelligence, on Fox Business, November 17
National Security Agency headquarters buildings at Fort Meade, Maryland, an agency file photo
NSA headquarters at Fort Meade, Maryland. Agency file photo, public domain.
Who blamed what for the November 2026 US outages: Microsoft a July fix, FAA a router flood, Chase a software bug, NSA patching
Four outages, four explanations, and only one points at patching.
Clayton’s interview on Fox Business’ The Claman Countdown, November 17, 2026.

Why officials point at patching

“AI is making it possible to identify vulnerabilities across enormous numbers of systems at unprecedented speed, creating enormous pressure on companies and government agencies to patch those vulnerabilities immediately, often all at once, putting tremendous strain on systems that weren’t built to handle that pace of change.”

Sen. Mark Warner, vice chair of the Senate intelligence committee, in a post on X, November 17
Sen. Mark Warner in a grey suit and striped tie, in front of the US and Virginia flags
Sen. Mark Warner. Official portrait by Ryan Donnell, US Senate, public domain.

Warner’s post said there’s no indication of a cyberattack, foreign interference or coordinated effort. “What appears to be happening instead is a consequence of how quickly artificial intelligence is changing the cybersecurity landscape,” he wrote. He added that the evidence so far “points toward legitimate efforts to secure our systems, not malicious activity.”

Sen. Mark Warner on X, November 17, 2026.

He made the point again in a short video the next day: “The recent widespread outages should be a wake-up call. AI is moving faster than our ability to manage its risks.”

Banks. Tech giants. Government systems. The recent widespread outages should be a wake-up call. AI is moving faster than our ability to manage its risks. We need stronger cybersecurity protections and common sense AI guardrails before the next disruption.

— Senator Mark Warner (@markwarner.bsky.social) 2026-11-18T15:53:03.099Z
Sen. Mark Warner on Bluesky, November 18, 2026.

Rep. Jim Himes, the top Democrat on the House intelligence committee, said more frequent outages are possible but called the patching pace “vital to shore up the security of all IT infrastructure.” The Financial Times quoted Anne Neuberger, a former deputy national security adviser and former NSA official: “In some cases, applying multiple patches will lead to outages. I suspect that is what occurred here.” Reuters quoted her, now a general partner at Andreessen Horowitz, saying: “When patching at scale, some can cause problems.”

The patch load

The numbers behind the pressure come from two trackers, and they don’t match exactly. Both show the same jump.

PeriodSecurity fixesCounted by
A year ago, monthly averageAbout 100Krebs on Security
October 20261,411BleepingComputer
October 2026More than 1,400Krebs on Security
November 20261,235BleepingComputer
November 2026Nearly 1,100Krebs on Security
Microsoft’s monthly security updates. Counts vary by outlet.

PHP and Java

Clayton pointed to PHP, and the Senate has too. Sens. Maria Cantwell and Mike Rounds wrote to Clayton on November 17 that “AI uncovered decades-old serious vulnerabilities in PHP, software used by millions of websites, leading to governments and companies shutting down their websites to patch the flaws.” Their letter says “our defenses are not keeping pace.”

What is PHP2Shell?

PHP2Shell is the name for two critical flaws in PHP, CVE-2026-109618 and CVE-2026-109619. Calif, OpenAI and Wiz found them. Either can let an attacker run code on a web server without logging in. The PHP team shipped emergency patches on October 21 in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. VirusTotal estimated more than 5.1 million PHP hosts were exposed online, and Cloudflare’s chief technology officer said the company was already seeing early attacks before the patches landed. The UK’s National Cyber Security Centre told organizations to update or take PHP systems offline until they could.

A second flaw followed. On November 17, the security firm Calif disclosed Java4Shell, a critical memory flaw in OpenJDK’s Base64 decoder tracked as CVE-2026-114938. Calif’s Quang Luong took an hour to find it and two more hours to build the first working exploit, for under $200 in AI tokens. Calif says Java runs at 90% of Fortune 500 companies. No universal exploit exists, and each target needs tailored steps. Oracle shipped a patch the same day.

CISA’s alert on X, November 17, 2026.
Java4Shell: one hour to find the flaw, two hours to build the first exploit, under $200 in AI tokens, Calif says
Calif found a Java flaw and built an exploit with AI in three hours for under $200 in tokens.

Attackers are speeding up too. An FBI alert on November 13 about an AI hacking framework called ARTEX said intrusions can go from first target to privileged access in under three hours.

Congress is reacting. On November 18, Reps. Morgan Luttrell and Ritchie Torres introduced the ROOT CAUSE Act, which would create a National Cyber and AI Investigations Board inside CISA to examine significant incidents and recommend fixes. The board would have no regulatory or enforcement authority.

What the evidence doesn’t show

Not every outage has a patching story. Bloomberg reported that Rapid7’s Christiaan Beek sees no public evidence that rushed updates caused these outages. “Complex systems fail in boring ways far more often than because of an adversary,” he said.

CyberWire Daily, November 18: “The sky is falling, but is it hacked?” The outages are one item in a 33-minute episode; its notes call the cyberattack fears “unfounded.”

Microsoft, the FAA and Chase name causes that don’t involve AI-found flaws, and the NSA’s own account doesn’t either. Neuberger said she suspects patching, which isn’t the same as knowing. Clayton’s account of the NSA is the only one from a sitting official that ties an outage to patching.

Nor are all AI-found flaws being exploited. VulnCheck counted 442 CVEs credited to Anthropic’s models in seven months, about 0.5% of the CVEs published this year, and only two are being exploited in the wild. PHP2Shell was different: Cloudflare saw attacks before the patches shipped.

What IT teams can do

CISA’s Java alert and Microsoft’s own report point to the same habits. None of them needs an AI to be involved.

  1. Find every Java runtime, including ones bundled inside other software. CISA says to do this first.
  2. Patch internet-facing systems first, and use compensating controls if patching has to wait.
  3. Check PHP versions. The fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and PHP 7 or earlier should move to a fixed release.
  4. Test patches on hardware that matches production. Microsoft’s load tests used weaker machines, and the bug only showed on newer ones.
  5. Roll out in stages, and keep spare capacity during failovers. Microsoft had nearly 14% of gateway capacity out when the bug triggered.
PHP branchFixed release
8.58.5.12
8.48.4.27
8.38.3.36
8.28.2.35
The PHP team’s emergency releases of October 21.
# Linux and macOS: list Java and PHP binaries (a starting point, not a full audit)
find / -type f \( -name java -o -name php \) 2>/dev/null

# Windows PowerShell: find Java runtimes
Get-ChildItem -Path C:\ -Filter java.exe -Recurse -ErrorAction SilentlyContinue | Select-Object FullName

Related on GREEENER.ai:

Three of the graphics in this piece, side by side:

Looking ahead, Microsoft’s final report on the 365 outage was due November 20 and we haven’t seen it yet, the FAA still has no root cause, and Microsoft’s next Patch Tuesday lands December 8. For IT teams in New Zealand and Australia, the Microsoft failure carries the practical lesson: test patches on hardware that matches production, stage rollouts, and keep spare capacity for failovers. The Java and PHP alerts apply here too. Find every runtime, including those bundled inside other software, and patch internet-facing systems first.

Sources