Entities

Entities collected from this article, grouped for quick reference and copying. Inclusion does not establish malicious activity. Article links appear separately at the bottom as references.

The National Security Agency's classified internal network went down on Tuesday, November 17, while the agency patched its systems. NSANet carries the classified communications NSA employees share internally, and six people familiar with the matter told CNN it was down. Director of National Intelligence (DNI) Jay Clayton said on Fox Business the same afternoon the outage came from patching, and some systems did not come back up as expected. CNN reported the patches addressed major software vulnerabilities discovered in October.

Clayton did not name the software, but CNN and Fox Business both identified the vulnerabilities as the PHP flaws known as PHP2Shell. Wiz disclosed CVE-2026-109618 and CVE-2026-109619 on October 21. The memory corruption flaws let an unauthenticated threat actor execute code remotely or read sensitive process memory, and nearly every PHP release since 5.4 carries at least one of them. Wiz used large language models to find the flaws and build working exploits, the same AI-driven acceleration I examined in Microsoft's record patch volume.

The Cybersecurity and Infrastructure Security Agency (CISA) told organizations the same day to patch immediately or take PHP systems offline, and the NSA urged immediate patching across the US government. Exploitation attempts had already begun.

Operation Timeline

Trace the events, turning points, and connections behind the analysis.

PHP2Shell and NSANet Timeline

Key events from the first recorded PHP2Shell exploitation attempt in October 2026 to the NSANet outage on November 17, 2026.

View Timeline Hide Timeline
  1. October 17, 2026

    Amazon Records a Pre-Disclosure Attempt

    Global

    Amazon Threat Intelligence records a PHP2Shell exploitation attempt against its MadPot honeypots from a commercial anonymization network, four days before disclosure. Amazon cannot determine how the threat actor learned of the embargoed flaws.

  2. October 21, 2026

    Wiz Discloses PHP2Shell

    Global

    Wiz discloses CVE-2026-109618 and CVE-2026-109619, memory corruption flaws allowing unauthenticated remote code execution or memory disclosure in nearly every PHP release since 5.4. PHP releases fixes the same day.

  3. October 21, 2026

    CISA Orders Patching or Disconnection

    United States

    The Cybersecurity and Infrastructure Security Agency tells organizations to patch PHP immediately, prioritizing internet-facing systems, or take PHP systems offline until patched.

  4. October 21, 2026

    NSA Urges Government-Wide Patching

    United States

    The National Security Agency warns cyber actors are likely to weaponize PHP2Shell and calls for immediate patching across US government departments and agencies.

  5. October 30, 2026

    PHP2Shell Exploited Against Check Point Gateways

    Israel

    A threat actor gains initial access through Check Point Mobile Access portals using PHP2Shell, escalates to root, and deploys the destroy_v6 wiper against Israeli organizations in the first wave.

  6. November 17, 2026

    NSANet Goes Down

    Fort Meade, Maryland

    The NSA's classified internal network is down on Tuesday, according to six people familiar with the matter. When the NSA began patching is not public.

  7. November 17, 2026

    NSA Declares Code Yellow

    Fort Meade, Maryland

    An NSA voicemail recording tells non-emergency staff to arrive in staggered shifts and emergency staff to report as usual. Some work moves to other NSA facilities.

  8. November 17, 2026

    NSA Cites Scheduled Maintenance

    Fort Meade, Maryland

    The NSA describes temporary degradation during scheduled routine maintenance, saying mission-critical capabilities remain fully operational.

  9. November 17, 2026

    DNI Ties the Outage to Patching

    United States

    Director of National Intelligence Jay Clayton says patching left some NSA systems unable to come back up, with no indication of a coordinated or state-sponsored cyber attack.

  10. November 17, 2026

    NSA Returns to Code Green

    Fort Meade, Maryland

    The NSA voicemail recording tells employees to report as scheduled Tuesday evening. A source tells CNN restoration of NSANet is ongoing but not complete.

Amazon Threat Intelligence recorded a PHP2Shell attempt against its MadPot honeypots on October 17, four days before disclosure, from a commercial anonymization network. Amazon could not determine how the threat actor learned of the embargoed flaws. Threat actors went on to exploit PHP2Shell in attacks on Check Point gateways beginning October 30 and in the attacks on PAN-OS, the Palo Alto Networks firewall operating system, I examined earlier.

The NSA described the event Tuesday afternoon as "temporary degradation during scheduled routine maintenance," saying some internal systems were affected while mission-critical capabilities remained fully operational. A voicemail recording told non-emergency staff at the Fort Meade, Maryland, headquarters to arrive in staggered shifts under a "code yellow," and CBS News reported some work moved to other NSA facilities. The recording returned to "code green" Tuesday evening.

Clayton said he saw no indication of a coordinated or state-sponsored cyber attack behind this outage or the other recent outages. On November 13, the Federal Aviation Administration (FAA) grounded flights nationwide after legacy equipment became unstable under data flooding its network, traced partly to a site where its network provider L3Harris was deploying a new router.

A current and a former US official told CNN the outage would not affect the agency's ability to send urgent intelligence to President Trump, who is traveling in Asia. A source from a Five Eyes country and a former US intelligence official told CNN intelligence sharing with Five Eyes partners was unaffected. A source told CNN restoration of NSANet was ongoing but not complete, and the NSA has not said whether NSANet is fully back.

The agency has not named the patched software, the systems failing to return, or how long the degradation lasted. Clayton's account also does not establish PHP ran on NSANet itself, since the patched component could be a service the network depends on. If the patch was for PHP2Shell, the outage came 27 days after the NSA urged immediate patching across the government, and the agency has not said whether Tuesday's maintenance was the first phase of that work.

Remote exploitation from the internet is an unlikely path into NSANet. Top secret networks sit apart from the Non-classified Internet Protocol Router Network (NIPRNet) and the internet, and authorized transfers pass through cross domain solutions, controlled interfaces held to NSA standards. The realistic routes in are insiders, removable media, and software carried across those interfaces. In 2008, a flash drive carried malware into classified military networks. Little is public about NSANet's design, so separation lowers the odds of a remote attack without excluding other routes.

The disruption fell on November 17, the date a viral hoax had set for a cyber attack cutting power and internet service, which I examined in my November 17 brief. I found no posts yet citing the outage as proof. A real failure of a classified network on the named date still hands the next version of the rumor its evidence.

The DNI's on-record account, the NSA's statement, and two sources speaking to CBS all point to maintenance or patching, and none of the reporting describes an intrusion. I assess with high confidence a maintenance failure caused the outage.

I assess with moderate confidence malicious activity played no part, because no investigation has been published and an insider or compromised update could remain invisible in first-day accounts. The link to PHP2Shell rests on how CNN and Fox Business read Clayton's remarks, so I hold it at moderate confidence until the NSA names the patch.

If that reading holds, the NSA faced the same choice it put to the rest of the government. Leaving PHP2Shell unpatched left systems open to unauthenticated code execution, and patching took down the classified network carrying the agency's own work. Every organization faces that choice on the same compressed timeline, so each needs a tested rollback, a map of the systems depending on the software being patched, and a continuity plan ready before the patch goes in.