The October 2026 PHP security update fixes php2shell, two critical bugs that can allow unauthenticated remote code execution. Here is what they are, who is at risk, how to update on common setups, and what to do on PHP 8.1 and older.
Running Magento, WordPress or any PHP app in Docker? The php2shell security release will not reach your containers through the host. Here is how I update PHP in a Docker container: pull or rebuild, recreate, verify php -v, and close dev ports on the LAN.
My CloudPanel VPS had ten PHP-FPM versions running, six of them end of life. With the php2shell bugs out, here is how I proved none of them served a request, switched them off with systemctl, and kept a one-line rollback, plus what to do if a Magento store still needs old PHP.
php2shell leaked before the patch, so the first question is not when to update PHP but whether someone already got in. These are the read-only checks I ran on my own Magento VPS: worker processes, access logs, changed files and the Magento database.
php -v shows one PHP, but most servers run several at once: CLI, a PHP-FPM service per version, Docker containers and control panel builds. Here is how I found all of them on my own VPS before the 21 October 2026 PHP security release.