in

DNI Jay Clayton: NSA Blackout Was Patch Screwup, Not a Hack

The latest drama at the National Security Agency looks less like a clever foreign cyberattack and more like a bureaucratic face-plant. Director of National Intelligence Jay Clayton told Congress the NSANet outage was not a coordinated, state‑sponsored hack. Instead, maintenance and hurried patching of dangerous PHP vulnerabilities — CVE-2026-109618 and CVE-2026-109619 — are the likeliest culprits. That should make every taxpayer uneasy and every tech vendor squirm.

DNI: Not a State-Sponsored Attack

DNI Jay Clayton made the blunt point to lawmakers: this was not a coordinated attack by an adversary. The classified internal network went offline during routine updates and staggered work schedules known inside the agency as Code Gray. The network came back up, mission‑critical systems stayed running, and analysts used backup channels to keep key operations moving. Fine — but “not an attack” is not the same as “no problem.”

The Patch That Tripped Us

What tripped the NSA was a rush to apply fixes for two severe PHP flaws. These CVEs rate very high for danger and affect many releases of PHP — the language that runs most of the web. Security firms recently flagged the bugs, and the FBI, NSA, and CISA warned organizations to patch immediately or pull affected systems offline. The NSA followed that guidance and then, predictably, ran into trouble. Too many legacy systems and overly complex network compartments meant the patching process caused outages instead of preventing them.

Security Theater vs. Security Hygiene

Sen. Mark Warner suggested the explosion of AI tools is making vulnerability hunting faster and patching more urgent. He’s right that tools find holes faster. But here’s the blunt truth conservatives should say out loud: blaming AI or foreign hackers misses the point. The problem is how we manage and maintain critical systems. Rushing dozens of patches in a week because a vulnerability is flashy does not equal smart defense. It equals sloppy operations. If we want real security, we need better testing, better staging, and fewer legacy systems that fail when you touch them.

What This Means for National Security

This outage reached beyond Maryland — it affected the NSA’s cryptologic center in Georgia, which handles signals and Middle East operations. That’s the nerve center for intelligence during a time of real conflict. Officials used backups and said the most sensitive collection continued. Still, the episode is a warning: when systems are brittle, our ability to respond quickly in a crisis can be degraded. Recent outages that also hit the FAA and major email systems show this is a pattern, not a one-off embarrassment.

Bottom Line

We should be relieved there was no foreign hand behind this particular outage. But relief is not a strategy. Congress and the agencies need to stop treating modernization as a buzzword and start funding sensible upgrades, disciplined patch management, and real testing. And vendors who ship decades‑old code with show‑stopping bugs should answer for it. In the meantime, let’s call the episode what it is: a wake-up call, not a conspiracy. Now fix it — quickly, quietly and without the theater.

Written by Staff Reports

Denmark Unanimously Approves Trump-Brokered Greenland Security Deal

Denmark Unanimously Approves Trump-Brokered Greenland Security Deal

Anthropic IPO hits $1T paper valuation — where’s the profit

Anthropic IPO hits $1T paper valuation — where’s the profit