PHP’s October patch stopped the original PHP2Shell exploit. Researchers at Depthfirst found another way around it. The new flaw, CVE-2026-126714, carries a 9.2 severity score and can let a remote attacker execute code with the privileges of the PHP worker.
‼️ BREAKING: Researchers broke past PHP's fix for the php2shell flaw and can again run their own code on web servers, no login needed.
Security firm depthfirst says the latest PHP releases are still vulnerable. The bug, CVE-2026-126714, is rated 9.2 out of 10.… pic.twitter.com/vtz0pBYlZC
— International Cyber Digest (@IntCyberDigest) November 19, 2026
The trick is in PHP’s file-based session storage. An interrupted write can leave pieces of two different sessions stuck together. PHP later reads the corrupted file and can deserialize attacker-controlled objects. No login is required, and the target site does not need an upload form. But exploitation still depends on conditions including control over session data and a suitably timed interruption.
One correction: PHP released fixes on November 19. The affected versions include PHP 8.5 before 8.5.13, 8.4 before 8.4.28, 8.3 before 8.3.37 and 8.2 before 8.2.36. Depthfirst’s technical page contains a version-table inconsistency, but PHP’s official advisory lists those releases as patched.
https://depthfirst.com/research/phpaftershell
https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
If you got something out of this, please chip in to keep this site running, or subscribe to go ad-free.
1 view