Outdated software is an open door
What PHP2Shell, Node2Shell and React2Shell reveal about updates, runtimes and responsibility
October 21, 2026 was a long day for many IT departments. Two of the most widespread foundations of the internet received urgent security updates on the same day: PHP, which runs WordPress among many others, and Node.js, the runtime behind countless modern web applications. In the worst case, both flaws let attackers run their own code on a server. And back in December 2025, React2Shell had already shown how fast attackers move today.
For law firms, legal departments and other offices, this sounds like a topic for specialists at first. But the most important lesson from these three cases has little to do with technology. It comes down to a question every management team should be able to answer: who actually takes care of updates here – and how quickly?
Three vulnerabilities, one pattern
React2Shell: hours, not weeks
On December 3, 2025, a vulnerability in React Server Components went public – a technology built into the popular web framework Next.js, among others. It received the highest possible score of 10.0 on the CVSS scale: attackers could run code on the server without logging in. According to Amazon, the first exploitation attempts began within hours of disclosure.
PHP2Shell: attacks before the patch
With PHP2Shell (CVE-2026-109618 and CVE-2026-109619), things went even worse. Both flaws are rated 9.2 out of 10, and the PHP developers had announced an unscheduled update for October 21. But in the night before the release, details leaked: at 02:29 UTC they appeared on VirusTotal. At 07:34 UTC, hosting providers reported the first attacks – more than six hours before the patch came out at 13:52 UTC. Security researchers had shown that the flaws allow unauthenticated takeover of WordPress, Drupal and Joomla installations.
Another figure is even more telling: of the PHP services on the internet whose version can be identified, around 79 percent run on branches that no longer receive regular updates at all.
Node2Shell: the flaw in the component nobody thinks about
Node2Shell (CVE-2026-111497), now also called HTTP2Shell, sits in an inconspicuous building block: the Brotli decoder, which unpacks compressed data. Node.js ships with it built in, and Node.js isn't alone. curl, widely used Python HTTP libraries and proxies such as Envoy use the same code. A crafted data stream is enough to corrupt memory.
Fixed Node.js versions 22.23.4, 24.22.1 and 26.12.1 were released on October 21. Release lines whose support has already ended won't get a fix. No attacks in the wild had been reported as of October 22, but researchers had already achieved code execution in the lab.
What the three cases have in common
The window is gone. Today, only hours pass between the disclosure of a vulnerability and the first attacks; with PHP2Shell, the attacks even came before the patch. If you install updates once a quarter, you're weeks too late when it matters.
Outdated means permanently open. For software whose support has ended, there is no patch to wait for. The hole stays. The roughly 79 percent of PHP installations show how common that is.
“Running” doesn't mean “maintained.” Many applications now run in containers whose versions are fixed when the image is built. An update to the runtime only helps once the image has been rebuilt and redeployed. Until then, the old, vulnerable version simply keeps running.
The most dangerous dependency is the one you don't know about. Before Node2Shell, hardly anyone would have known there was a Brotli decoder inside their software. And React2Shell also hit applications that didn't explicitly use Server Functions.
What modern standards mean in practice
Modern infrastructure has little to do with trends. It's about being able to patch at any time. In practice, that means:
- Only using versions that are still supported, and having the end of support in your calendar.
- Knowing what's running: an up-to-date list of all components and dependencies, a so-called software bill of materials (SBOM).
- Automating updates where possible, and being able to build and roll out new versions quickly.
- Keeping admin interfaces off the open internet.
- Making backups and testing regularly whether they can be restored.
The legal framework is tightening
Lawmakers are raising the bar, too. Since December 6, 2025, Germany's NIS-2 Implementation Act has been in force. It requires around 30,000 companies to run systematic risk management and explicitly holds management accountable. Since September 11, 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities within 24 hours under the EU Cyber Resilience Act. And for law firms, professional secrecy adds another layer – and with it the question of how well maintained the systems are that hold client data.
Eight questions to ask your IT team or software vendor
- Which runtimes and versions does our software use, for example PHP, Node.js or Java?
- When does support for these versions end?
- How quickly are critical security updates installed, and who is responsible?
- Is there an up-to-date list of all components and dependencies?
- Are containers and installations rebuilt and redeployed after an update?
- Which systems can be reached from the internet, and do they need to be?
- When did we last test whether a backup can be restored?
- Who tells us when a vulnerability like PHP2Shell becomes public?
How we handle it at Auxilico
We've set clear rules for our own products. We provide critical security updates within one day and less critical ones within one week. With hosting on our dedicated servers in Germany, we install them ourselves. If you run our software on your own hardware, we deliver the updates and your IT installs them. Every office has its own instance.
Outdated software feels safe for a long time, because nothing happens. PHP2Shell, Node2Shell and React2Shell show that this feeling is deceptive. The good news: most of these risks don't call for expensive specialist technology, but for order – knowing what's running and keeping it up to date. If you'd like to know how we organize hosting and updates for our modules, get in touch.
Sources
- AWS Security Blog: China-nexus cyber threat groups rapidly exploit React2Shell (CVE-2025-55182)
- Recorded Future: PHP2Shell Exploitation
- Qualys: PHP2Shell – Find, Mitigate, and Patch Now
- watchTowr: PHP2Shell RCE Exploited
- Aikido: Node2Shell (CVE-2026-111497)
- Aikido: Node2Shell evolves to HTTP2Shell
- IHK Darmstadt: NIS-2 obligations for companies (German)
- KPMG: CRA reporting obligations from September 11, 2026 (German)