The Week Everything Broke โ a short story
It started with the skies. On Friday, November 13, 2026, at about 3:30 p.m. Eastern, data began flooding the FAA's flight-data network โ roughly 1,000 connection attempts every four to five seconds. At 3:54 p.m. the FAA stopped every departing flight in the United States. The nationwide ground stop lasted until 8:15 p.m. โ four hours and twenty-one minutes. About 3,500 aircraft were already airborne; every one landed safely. The instability reached 17 of the FAA's 22 en-route control centers. Two sites were the suspected sources โ a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where contractor L3Harris had been deploying a new router. The broadcasting function blamed for the flood was later disabled on more than 60 similar Juniper routers. The FAA's words: based on all available evidence, there is no indication this was a cyberattack.
The cancellation count is where the weekend's retellings went wrong, so this page keeps both counters separate. The FAA's own later count for Friday is 12,462 cancellations, including 9,082 at major airlines โ with the FAA's own caveat that not all were directly caused by the ground stop. FlightAware counts 9,159 for the same day. Two honest counters, two totals; they are not averaged here.
The day before, Microsoft 365 had fallen over. Microsoft's preliminary post-incident review โ reported, with the final review due around November 20 โ describes a latent defect from a July fix in its networking gateway servers, a Teams failover onto those gateways, and about 14% of gateway capacity out of service. At the worst point more than 80% of the gateway servers were unresponsive; active impact ran 23 hours 50 minutes, November 12โ13, with Outlook hit hardest and longest.
Then, on Tuesday, November 17, came the Java act. CISA โ the U.S. cybersecurity agency โ issued a standalone alert: patch a critical flaw in Java, CVE-2026-114938, immediately. The flaw, nicknamed Java4Shell, is a heap out-of-bounds write in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine. A 65-character input โ sixty-four letter A's and one equals sign โ makes the engine allocate a 50-byte array and then write a full 64 bytes into it: 62 bytes past the end. It was found by researcher Quang Luong at the startup Calif, who told OpenAI's Codex to audit the engine โ about an hour to find it, about two more hours to a first exploit, under $200 in tokens. (Press reports name the model "GPT-6 Cyber"; Calif's own write-up names only Codex, so the model name is labelled reported, not confirmed.)
Java4Shell was the second act, not the first. A month earlier the same firm had found two critical flaws in PHP โ PHP2Shell. And patching those PHP flaws is what broke something at the NSA this same week: the Director of National Intelligence said the NSA's classified NSANet went down on November 17 because systems did not come back up after the PHP patching. The NSA's own statement calls it scheduled routine maintenance. Restoration has not been confirmed. A third AI-found flaw, in the Brotli compression library โ a library, not a language โ rounds out the pattern: the auditors and the attackers now share the same tools, and the rate is the story.
Two honest scores close the story, and they are not merged: Oracle scores Java4Shell 8.1 (CVSS v3.1, attack complexity High, "difficult to exploit"); Calif scores it 9.2 (CVSS v4.0, no vector published). It is not in CISA's Known Exploited Vulnerabilities catalog. As of November 17 there are zero confirmed production compromises and zero reported in-the-wild exploitation. The crash is independently confirmed; Calif's product-level code-execution claims are its own, unconfirmed; Wiz says it proved code execution against Jenkins, Confluence and Tomcat in its labs. The doors on this page are the response: check whether you are exposed, then patch.
Every event in this story is drawn from the verified research behind this site: the FAA's own Q&A, Microsoft's preliminary post-incident review as reported, CISA's November 17 alert, Oracle's November 2026 Critical Security Patch Update, the CVE record, and Calif's write-up โ each claim labelled verified or reported in the underlying research, and disagreements kept separate, never averaged.