PHP has shipped two rounds of critical security fixes in five weeks. The first, known as php2shell, is already being exploited by attackers. The second, released on 19 November 2026, fixes seven more critical remote code execution flaws. If your websites or applications run on PHP, including WordPress, Laravel, Magento and most hosting control panels, you need the latest patch release.
Update to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (or 8.6.0). If you still run PHP 8.1 or older, there is no fix: upgrade, or take those systems offline until you can.
October: php2shell (CVE-2026-109618 and CVE-2026-109619)
On 21 October 2026 the PHP project disclosed two critical flaws that allow unauthenticated remote code execution. In other words, an attacker on the internet can run code on your server without logging in. According to the US Cybersecurity and Infrastructure Security Agency (CISA), they affect every PHP installation that serves web requests, including Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed.
The fixed versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. On 26 October, CISA added both flaws to its Known Exploited Vulnerabilities catalogue, which means attacks are happening in the wild.
November: seven more critical fixes
PHP's regular release on 19 November fixed seven critical remote code execution flaws plus ten high and medium-severity issues. Highlights:
- CVE-2026-115560: session upload progress data can be written in one format and read in another, which can lead to code execution if the application contains a suitable "gadget chain".
- CVE-2026-129481 and CVE-2026-129182: use-after-free bugs that complete the fix for php2shell (CVE-2026-109619). If you patched in October, you still need this update.
- CVE-2026-126714: an interrupted session write can lead to attacker-controlled data being unserialised.
- CVE-2026-129289: a PHP-FPM request smuggling flaw. Unread request data on a reused FastCGI connection can be turned into a separate request that bypasses your front-end routing.
- CVE-2026-129474: a use-after-free in PHP 8.5 and later.
- CVE-2026-129496: a use-after-free in the timezone cache that can corrupt memory.
All of these are fixed in PHP 8.6.0 and 8.5.13. Most are also fixed in 8.4.28, 8.3.37 and 8.2.36, released the same day. PHP 8.6.0, the new major release, also came out on 19 November.
Which version should you be on?
| Branch | Minimum safe version | Notes |
|---|---|---|
| PHP 8.6 | 8.6.0 | New release, 19 November 2026 |
| PHP 8.5 | 8.5.13 | Fixes all November critical flaws |
| PHP 8.4 | 8.4.28 | Plan the move to 8.5 or 8.6 |
| PHP 8.3 | 8.3.37 | Security fixes only |
| PHP 8.2 | 8.2.36 | Security support ends 31 December 2026, so upgrade soon |
| PHP 8.1 and older | None | End of life: no fixes. Upgrade urgently |
What to do now
1. Find every PHP installation
Run php -v and php-fpm -v on each server, and check container images, staging servers and hosting control panels (cPanel/WHM, Plesk and similar often ship their own PHP builds). PHP is often hidden inside other products.
2. Update and restart
Install the fixed packages from your distribution or PHP repository, then restart PHP-FPM and your web server so the new code is actually running. Internet-facing sites come first.
3. Interim protections if you can't patch today
- For CVE-2026-115560: set
session.upload_progress.enabled = 0in php.ini and restart PHP workers, unless your application relies on upload progress. - For CVE-2026-129289: turn off persistent (keep-alive) connections between the web server and PHP-FPM. In nginx, make sure
fastcgi_keep_conn on;is not set. - Use a web application firewall such as AWS WAF as an extra layer. It helps, but it is not a substitute for patching.
4. Check for compromise
Because php2shell is being exploited, look for PHP worker processes starting shells or downloading tools, unexpected new PHP files in web folders, and unfamiliar admin accounts in your applications. If you find anything, isolate the server and investigate before simply patching.
Need help?
Our managed cloud and security teams patch and monitor PHP and nginx stacks for clients across the UAE, Saudi Arabia and India. If you'd like us to check your servers, message us on WhatsApp. Running nginx in front of PHP? Read our nginx security update too.
Sources: CISA alert on php2shell, PHP 8 ChangeLog, SecurityWeek report on the November release. Check PHP's official advisories for the exact fixes in your branch.