Skip to content

NEWS

PHP2Shell: patch today, then perform due diligence in these four areas after patching

22 October 2026

← Back to News

On 21 October PHP shipped an emergency release for two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. Both let an attacker run code on a web server without logging in. Every version from PHP 5.4 through 8.5.11 is affected. The fixes are 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

The reaction told you how serious it was. The Dutch national cyber security agency took its own website offline, along with the Port of Rotterdam, Overheid.nl and several hospitals. Finland’s Valtori withdrew public network services. France’s Interior Ministry put local government sites into maintenance. Nintendo, Wikipedia and the Internet Archive pulled systems too.

Patching is urgent and it is the only complete fix. Once it is done or under way, four things decide whether it actually protected you.

  1. Restart. Your web servers and PHP-FPM processes need restarting before the patched code is serving traffic. A patched binary nobody restarted is not a patched system, and this is the most common way a team ends up believing it is covered when it is not.
  2. Find the installs you missed. PHP hides inside other software and will not always appear in your asset register. Check every host, container and machine image, not just the obvious web servers.
  3. Unsupported versions have options. PHP 8.1 and older get no fix from php.net, but that is not the end of it. Check your Linux vendor first, because Red Hat, Ubuntu and Debian have shipped patched builds for versions they still support. If there is no backport, moving to 8.2 or later is the only durable answer, so start compatibility testing now. If that cannot happen this week, paid extended support from a third party will get you a patched build. Failing all of that, take the system off the public internet or restrict it to known addresses behind a WAF, and treat that as a stopgap rather than a fix.
  4. Assume an exposure window. Several vendors reported exploit attempts, including Amazon from 17 October, four days before disclosure. If a server was internet facing and unpatched this week, go looking: unfamiliar files in the web root, scheduled tasks nobody created, new accounts, outbound connections from the web process.

One thing that catches people out: this is not a CMS problem. Updating WordPress, Drupal or Magento leaves the exposure exactly where it was, because the flaw sits in the PHP runtime underneath your application.

And if you take card payments, PCI DSS requirement 6.3.3 gives you one month for critical patches. That is the outer limit, not the target, and not the timescale your attacker is working to.

Whatever you do, write it down today. Evidence gathered this week is worth far more than evidence reconstructed eleven months later.