Blog

PHP Vulnerability 2026: A Timeline of the Year’s Critical Flaws

4 min read
Seismograph paper strip with a flat, quiet ink line from January to September that erupts into sharp, glowing magenta spikes in October and November. Beside it is the title "PHP Vulnerability 2026: A Timeline of the Year's Critical Flaws."

For most of 2026, PHP security looked routine. There were the usual fixes for bugs in individual extensions, such as an SQL injection flaw in the pdo_firebird driver made public in May, and nothing that forced an emergency response.

That changed in October. In the space of a month, PHP shipped an emergency patch for two critical flaws known as PHP2Shell, watched them get exploited in the wild, and then released fixes for 18 more vulnerabilities, seven of them critical. Every one of the critical flaws sits in PHP’s core engine rather than in a framework or plugin, so they affect almost every application built on PHP.

AI is a big part of why it happened now. Several of the 2026 flaws were found with AI-assisted research, including phpAfterShell, which security firm Depthfirst discovered using frontier AI models tuned for security work. Researchers can now dig through mature codebases like PHP’s much faster than before, and 2026 is the first year that’s shown up at this scale.

2026 PHP Vulnerability Timeline

The issues behind PHP2Shell were first spotted in a 2024 audit, but the remote code execution paths weren’t confirmed until several teams reported them in August 2026. From there, events moved quickly.

PHP2Shell and the Brotli flaw are the only 2026 PHP issues confirmed as exploited so far, which puts both on CISA’s list of known exploited vulnerabilities. The November flaws were patched before any public exploitation, so teams that patch now are still ahead of attackers on those.

The Critical PHP CVEs of 2026

PHP has published nine critical CVEs in 2026, every one rated 9.2 under CVSS 4.0. Here they are in one place.

The pattern is clear. Almost all of them are memory-safety or session-handling bugs deep in the engine, and several only apply under specific configurations. That’s why the same release can be critical for one server and irrelevant to the one next to it.

Which PHP Versions Are Safe in 2026

The November releases include the October PHP2Shell fixes, so a single upgrade covers the whole year. After upgrading, restart PHP-FPM or Apache so the running workers pick up the new code.

PHP 8.1 and earlier are end-of-life and won’t receive official fixes, yet PHP2Shell affects code all the way back to PHP 5.4. If you still run an older branch, your options are to upgrade to a supported version or move to a commercial extended-support build that backports the fixes. Leaving it as is means leaving an actively exploited flaw open.

Lessons From PHP’s 2026 for Running PHP Safely

The main lesson from PHP’s 2026 is that a flaw in the runtime is a flaw in everything you’ve built on top of it. You can’t wait for a framework or CMS update to protect you, so the response has to happen at the level of the runtime itself.

Three habits make that manageable:

  • Know where PHP runs. Keep an asset inventory that tracks PHP versions across servers, containers, vendor software and appliances, not just your own applications.
  • Patch the runtime fast. PHP2Shell was exploited before patches existed and was widely attacked within days of disclosure. Critical runtime fixes need a days-long timeline, not a monthly patch cycle.
  • Expect a second wave. The November release came directly out of research into the October fix. After any major disclosure, plan for follow-on advisories and watch for them.

None of this is new to vulnerability management. 2026 simply showed how much it costs when the runtime under most of the web isn’t treated with the same urgency as the apps running on it.