As a string of high-profile tech outages rattled businesses over the past week, the organizations involved — Microsoft, the FAA, JPMorgan Chase and others — pointed to botched upgrades and technical glitches, not hackers. But what an expert on this issue, the National Security Agency (NSA), said its outage was caused by was its scramble to fix PHP2Shell. This raises two questions: how many other organizations are patching in a hurry, and how many checked first whether someone could possibly already be inside?
The outages follow the urgent calls late last month for patching what’s referred to as PHP2Shell, a pair of flaws in PHP, the programming language behind roughly 70 percent of websites worldwide with an identifiable server-side language.
On Aug. 11, researchers reported two critical flaws in it. They were proven by Aug. 15 and fixes were being designed and were under a quiet, coordinated embargo set to lift Oct. 22. But on Oct. 20, details leaked online and the PHP Foundation pulled its release forward a day to Oct. 21.
The same day, the NSA said the vulnerability “could allow attackers to take control of affected web servers without prior access or authentication. Such an access vector could help attackers steal sensitive data, disrupt services, or move deeper into a network … Cyber actors are likely to weaponize PHP2Shell vulnerabilities. These risks are serious enough to require immediate patching across United States Government departments and agencies.”
When the PHP issue became public, attackers didn’t wait for patching. It’s also unknown how long attackers may have known about these flaws, which sat in PHP since about 2012.
Amazon later traced the earliest known exploitation attempt to Oct. 17, four days before the patches were released, and Cloudflare reported that attempts grew from thousands before the patch to millions by the morning of Oct. 22. By Oct. 25, researchers had documented a suspected China-linked operator using the flaws, chained with a Linux privilege-escalation bug, to take over 25 servers — two or three of them in an environment connected to the U.S. government.
A key problem with rapid PHP patching is that it doesn’t evict anyone who already may have walked through security protections. Any organization that installed the fix without first assertively hunting for signs of intrusion could simply have locked an intruder inside.
Another challenge is that many IT teams don’t know where PHP is running. The Cybersecurity and Infrastructure Security Agency warned that PHP is often a component of other software and may not be directly observable; it is frequently buried in things that run on vendors’ patch schedules, not the customer’s.
Closer to home, the League of Minnesota Cities warned member cities in October that they could be using PHP directly or through a vendor. And an organization that can’t find its PHP can’t tell which systems to check for activity since Oct. 17.
As for the other outages, Microsoft attributed its Microsoft 365 failure to an earlier network-capacity upgrade exposed by a later network change. The FAA ground stop traced back to a new router that made more than 1,000 connection attempts every four to five seconds and overloaded the FAA’s communications network. JPMorgan Chase called its Nov. 16 slowdown a technical problem, not a cyberattack. And the Department of Homeland Security says the outages are not connected and officials have found no evidence that the Microsoft or FAA outage was a cyberattack, either.
The one outage officially tied to PHP is the NSA’s own. Its classified internal network was down Nov. 17, and Director of National Intelligence Jay Clayton said on Fox Business that work to fix the PHP flaws was behind it. “The patching that has gone on following that has caused some of these systems to not come back up when you patch them as expected,” Clayton said. “That is what has happened at the NSA today.”
The takeaway from all of this is that fixing the PHP matter takes more than installing a patch. If they haven’t already, organizations should confirm every PHP instance, including vendor-hosted sites and appliances, is on a fixed or vendor-backported version; review web server logs back to at least Oct. 17, 2026, for unusual requests; and scan for unfamiliar files, scheduled tasks or accounts created during that window. And as the NSA learned, patches for critical systems need testing before they go live.
