JA

What is the PHP vulnerability Japan's Prime Minister called an "urgent request"? Node.js fixed one the same day, and other languages are probably next

Here is what this post covers:

Introduction

On the night of October 21, 2026, Japan’s Prime Minister, Sanae Takaichi, posted on X what she called an urgent request to act that very night. A serious vulnerability had been found in PHP, a programming language widely used to build websites, and she asked site operators to get ready to apply the fix, due out at 11 p.m. Japan time, as soon as it landed. She even said that temporarily taking a site offline is a valid option if the fix can’t be applied quickly.

It is unusual for a prime minister to personally call attention to a vulnerability in one piece of software. She also took her own website offline for a while (it is back up now).

The same day, Node.js, which runs this blog, also shipped versions that fix several vulnerabilities. I just finished updating.

In this post, I explain what was found in PHP and Node.js in terms a non-engineer can follow. Then, because AI found both sets of vulnerabilities, I look at what is likely to happen next.

The PHP vulnerabilities

PHP is a programming language that runs behind the scenes of a website, on the server. WordPress, which powers many blogs and shop sites, is built with PHP. According to W3Techs, about 70% of the sites whose server-side language is known use PHP.

Two vulnerabilities were found, and the researchers who found them named the pair “PHP2Shell.” Each scores 9.2 out of 10 for severity. The scariest part is that an attacker can take over a server just by sending it data, with no login needed. Once a server is taken over, the attacker can rewrite the site or steal customers’ information.

Let me explain how it works with a city hall counter. PHP handles visits to a website the way a clerk handles visitors, one at a time.

The first one (CVE-2026-109618) is a bug that appears when the server runs out of memory and the work stops partway. At the counter, it is like the clerk stopping halfway through filling in a form and leaving the half-written form on the desk. The person who tidies up later takes that half-written form for a proper one and processes it.

The second one (CVE-2026-109619) is a bug where information from the previous visitor stays behind. The previous visitor’s papers have been thrown away, but a note saying “papers are in drawer 3” is still on the desk. When the next visitor comes, the clerk reads the note and opens drawer 3, but what is inside is no longer the same. An attacker can put their own papers in that drawer.

The affected range runs from PHP 5.4, released in 2012, up to the latest 8.5.11. The fixed versions are 8.5.12, 8.4.27, 8.3.36, and 8.2.35, and no official fix is coming for PHP 8.1 and earlier, which are past end of support. A site stuck on an old PHP has no choice but to move to a newer version.

There was a reason for the urgency. According to Amazon’s research, an attack aimed at this vulnerability was already seen on October 17, four days before it was made public. After disclosure, it was reported to be widely exploited. Once a fix is out, attackers can read what it changes and learn how to attack, so every night of delay counts.

If you don’t know whether your company’s or shop’s site runs on PHP, the quickest thing is to ask whoever built or manages it. If you use a rental server, also check for notices from the provider.

The Node.js vulnerabilities

Node.js is software that lets JavaScript, which normally runs in the browser, run on a server too. Like PHP, it is widely used behind web services.

On October 21, Node.js released versions that fix 10 vulnerabilities. Four are rated “high” in severity. It hasn’t caused as much of a stir as PHP, but the contents are not minor.

The most serious one is a bug in the code that restores data compressed in a format called Brotli (CVE-2026-111497). On the web, data is often compressed to cut traffic and then restored by the receiver. In this step, the code could write more data than the box it had prepared could hold. Data that spills out of the box overwrites important information next to it. If an attacker sends compressed data crafted for the purpose, the server can be taken over, just as with PHP.

This bug is not unique to Node.js. The Node.js fix pulls in a fix from Google, which develops Brotli. Other software that includes the same component needs to be checked too.

Of the other three “high” ones, two let an attacker slip past the check that confirms the other side of an encrypted (TLS) connection is genuine. Writing the other side’s address a little differently, for example using full-width digits in an IP address, is enough to make the code accept an impostor as the real thing. The remaining one is a bug where a special “end here” character placed in the middle of a server name (domain name) makes the name get cut off at that point.

The Node.js notice doesn’t say any of these are already being exploited. The fixed versions are 22.23.4, 24.22.1, and 26.12.1.

This blog is also built with Node.js. But Node.js only runs when the pages are built before publishing, so the impact is close to nothing. I still moved from 22.23.2 to 22.23.4 to be safe. That is when I noticed what Dependabot does and doesn’t cover. Dependabot automatically updates the libraries you use, but it doesn’t bump the version of Node.js itself. So the libraries can be up to date while the Node.js that runs them stays old.

AI found them

The two sets of vulnerabilities have something in common. AI was used to find both.

PHP2Shell was found by a research team at the security company Wiz. According to Google Cloud’s post, Wiz combined several AI models and used them from finding the flaws through confirming the fix. The Brotli bug in Node.js was also credited in the official notice to the “OpenAI Codex Security” team, a product OpenAI built to look for vulnerabilities with AI.

This trend is not new. In January 2026, all 12 vulnerabilities disclosed in OpenSSL, a component of encrypted communication, were found by AI. OpenSSL is used on servers around the world for connections with the padlock mark.

PHP2Shell is a bug that has been there since the 2012 versions. We are now in an age when AI finds holes in old code that people overlooked for more than a decade.

The same goes for attackers. The Amazon research team points out that AI lowers the effort needed to turn a fix’s diff or a published advisory into a working attack. With PHP2Shell, attacks had already started four days before disclosure. The time between a vulnerability being found and being exploited keeps getting shorter.

My prediction

From here on, this is my prediction. Not just PHP and Node.js: I expect big vulnerabilities to keep turning up in other language runtimes and in the services built on them. I have three reasons.

First, the core of both PHP and Node.js is written in C or C++. Those languages make the kind of bugs we saw this time easy to introduce, such as “spilling out of the box” and “using something that was already thrown away.” The core of the Python, Ruby, and Java runtimes is also written in C or C++.

Second, everyone reuses the same components. Like Brotli this time, compression and encryption components are included in many pieces of software. When one hole is found in a component, everything that uses it has to be checked.

Third, the effort needed to look for vulnerabilities with AI has dropped sharply. Detailed reviews of old code that weren’t worth doing by hand can be repeated as many times as needed with AI. Defenders can use it to find and fix holes sooner, but attackers can use the same tool.

To be honest, large vulnerabilities found by AI in the Python, Ruby, and Java runtimes haven’t stood out yet. But when this much came out for PHP and Node.js on the same day, I think it is only a matter of time before the other languages get their turn.

So how do we prepare? First, know what your service runs on and which version. As with PHP this time, versions past end of support get no fix. Second, set things up so you can apply a fix the same day it comes out. Even with automatic updates like Dependabot, the language runtime is sometimes not covered, so you have to keep track of that yourself.

Wrap-up

Two vulnerabilities were found in PHP that let an attacker take over a server without logging in, and attacks started before they were made public. The Prime Minister’s “urgent request” reflects how short the time is between a fix coming out and attacks beginning.

The same day, Node.js also fixed several bugs, including one in the code that restores compressed data that could let an attacker take over a server. Both sets of vulnerabilities were found with AI, and the trend of AI finding holes left in old code is getting stronger.

I predict the same will happen in other language runtimes and services. The Prime Minister’s call this time asked people to apply the fix the same day it came out. Now is a good time to build a setup that makes that possible.

References