Light Mode Dark Mode
October 28, 20262 min read

PHP2Shell: What to do about the critical PHP vulnerabilities

261008_PHP2Shell_Vulnerability_blog_image_m1-02 3

 

On October 21, the PHP project released fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell. Either one can let an attacker run code on a PHP web server without logging in. Security vendors report public proof-of-concept code, and some researchers report attacks, though others have not confirmed them. Treat unpatched, internet-facing PHP servers as a priority.

Adaptiva does not use PHP for any systems, but your servers may be affected. Here is what to do:

  1. Identify where PHP runs, including copies bundled inside other applications, appliances, and containers.
  2. Update to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or to your vendor’s patched package, and restart PHP processes that are already running, as PHP’s advisories describe.
  3. Use Adaptiva to help deploy the update. Adaptiva customers can use OneSite Patch to deploy software updates to servers and to track deployment status. Plan the restart of PHP services as part of your rollout, and follow your maintenance windows.
  4. Review exposed systems for signs of compromise, as described in the Canadian Centre for Cyber Security alert.

The PHP project no longer updates PHP 8.1 and older, but some distributions, including Ubuntu, list patched 8.1 packages in their notices. If you run one, check your vendor’s advisory and plan a move to a supported version. A third flaw, CVE-2026-115560, is not addressed by the October 21 release. PHP’s October 23 advisory covers it.

For more details, read How to Respond to PHP2Shell.

Adaptiva customers can also find our official statement on the Adaptiva | Support Center.

See Adaptiva in Action

Watch How-to: PHP2Shell Vulnerability Investigation to see how to check the compliance state of a patch, create an ASAP strategy, and manually submit the latest patch. 

In Closing

Every day between disclosure and patching is a day of exposure, which is why the time-to-exploit window matters. Read more in Cyber Resilience Depends on Closing the Time-to-Exploit Gap. 

Sources

 

AdobeStock_488605053

Ready to Get Started?

Schedule a one-on-one demo today.

Request a Demo