On October 21, 2026, the PHP project shipped emergency releases for two critical flaws now widely called PHP2Shell. If you were looking for the PHP2Shell vulnerability patch, it is simple to state: PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35. The hard part is knowing every place you actually run PHP. This PHP RCE story is less about one server and more about the dozen you forgot.
What PHP Actually Shipped
The php.net security advisory says those four releases “fix two critical vulnerabilities that can allow unauthenticated remote code execution,” and that “All PHP users are strongly encouraged to update immediately.” The two bugs are:
- CVE-2026-109618, RCE via OOM corruption. In php.net’s words, out-of-memory handling “can interrupt PHP while internal request data is only partially initialized. Request cleanup may then treat the invalid data as valid.”
- CVE-2026-109619, RCE via stale global state. Request-owned internal state “can survive after its backing memory has been freed. A later request handled by the same worker may use that stale state before normal initialization resets it.”
On scope, php.net says this affects “all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.” It considers the risk “highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs.” The PHP Foundation’s post adds that remote code execution “was also confirmed on PHP-FPM through application-level code paths.” The PHP security team rates both at CVSS 9.2. The Foundation notes that the CVE IDs leaked a day early with “a wrong CVSS score of 10.0.”
On older versions, php.net says branches 8.1 and earlier “no longer receive updates from the PHP project.” The security team published “minimal source-backports” for people who build from source. Tenable’s FAQ says those backports cover PHP 7.4 through 8.1. It also cites Calif’s writeup as finding affected code going back to PHP 5.4.0, which gets no fix from the project.
Was AI Really Involved?
Yes, by the researchers’ own accounts, though not alone. The PHP Foundation describes a longer history. A Foundation-contracted core developer “found the first signs of the OOM problem” during a 2024 audit, but “no concrete vectors were found.” Then on August 11, 2026, “researcher Ryan A at Calif reported an unconditional remote code execution with the same root cause.” The Foundation credits Calif, Wiz, OpenAI Codex Security, OSTIF, and Quarkslab for research and disclosure.
Wiz’s research post, which is vendor research, says: “We used Wiz Atlas, Gemini 4 Argon and GPT-5.6 Sol throughout this research.” It says frontier models enabled them “to develop and adapt working exploits across multiple applications in hours.” Tenable says, “Calif and Wiz have both said they used AI models in their research.” So “found by AI” is shorthand. The underlying problem was spotted by a human in 2024, and AI models helped researchers prove it was exploitable this year.
What About “Most of the Web” and “15 Minutes”?
Wiz says PHP “powers 70% of all websites in the world.” Tenable cites a W3Techs figure that PHP is used by “69.3% of websites whose server-side language is known.” That measures how common PHP is, not how many sites are exploitable. Vulnerable versions, server mode, and protections all vary. So “much of the web runs PHP” holds up. “Most of the web is exposed” goes beyond what the sources measured.
The “15-minute clock” in the original headline traces to a pre-release prediction that mass attacks would start within 15 minutes of the fix. None of the primary sources I read gives that as a measured fact, so I dropped it. What the sources do say about exploitation varies by date and by who is reporting. Tenable quotes Cloudflare’s CTO saying the company is “seeing early attacks emerging,” and says watchTowr reports “exploitation attempts against both.” Those are vendor observations, not counts of breached sites, and I would not assume you have more time than they suggest.
Find Every PHP Runtime You Actually Run
This section is my own recommendation as an operator, not guidance from PHP or any vendor. PHP often ships inside other software, so the hard part is finding it. Here is how I would do it.
- Distro packages. On each host, check the package manager, not just php -v. A box can have several PHP versions installed side by side. Php.net says distributions and LTS vendors got the patch early, so compare against your vendor’s advisory, since backported fixes may keep an older version number.
- CLI vs. FPM vs. mod_php. The CLI binary on your PATH may not be what serves web traffic. Check the FPM service and the Apache module separately. Then restart them. A patched package doesn’t help a worker that is still running the old code.
- Containers. Search image registries and running containers for PHP base images and bundled runtimes. Rebuild from patched bases and redeploy. Pulling a new tag does nothing to running pods.
- Managed hosts and platforms. For shared hosting, managed WordPress, or PaaS, ask the provider in writing which version you are on and when they patched.
- Appliances and bundled apps. Admin panels, monitoring tools, and vendor appliances often embed PHP. These are the hardest to see and the easiest to forget.
- End-of-life branches. Anything on 8.1 or older needs an upgrade, a vendor backport, or a decision to take it offline. php.net says these branches get no project updates, only the minimal source backports.
Here is a hypothetical. Your web fleet is patched by lunch. Then someone remembers the old reporting server in a closet, running a vendor’s dashboard on PHP 7.x behind a forgotten port forward. That is the box your inventory needs to find. It is my illustration, not a reported case.
If you need time, php.net lists interim settings, such as memory_limit=-1 enforced at the pool level and session.upload_progress.enabled=0. It is blunt that they “reduce exposure to specific attack paths but do not make an installation safe.”
The Bottom Line
Two engine-level RCE flaws, confirmed by the PHP project, patched in four supported branches, with exploitation attempts reported by security vendors. AI helped make them exploitable. It did not invent them. Patch, restart, rebuild, and then go hunting for the PHP you didn’t know you had.
