TL;DR
- PHP released security updates for all supported versions on 19 November 2026. Fixed versions: 8.5.13, 8.4.28, 8.3.37 and 8.2.36.
- The release fixes 18 CVEs, including CVE-2026-129289, a critical PHP-FPM request smuggling flaw (CVSS 9.2). With a single request, an unauthenticated attacker can run PHP code as the worker if your web server reuses connections to PHP-FPM and an application opens
php://inputwithout reading it fully. - PHP rated the highest-severity issue critical. According to PHP, the critical issues only affect installations with non-default configuration or uncommon setups.
- CVE-2026-115560 is one of several critical issues in this release. If you already set
session.upload_progress.enabled=0and restarted your PHP workers, the published attack path for that CVE is mitigated, so we don’t recommend taking your application offline for it while you wait to update. That setting doesn’t cover the other critical issues, so upgrade as soon as you can. - Aikido Images for PHP already include these fixes for Aikido users, with more images on the way. Everyone else can pull them from the public ECR gallery.
- To check whether you're affected, click "Am I affected?" on your Aikido dashboard.
Am I affected?
Click "Am I affected?" on your Aikido dashboard to see whether your projects run an affected PHP version. Any PHP version earlier than the fixed versions in this release is in scope, though not every issue applies to every branch. The PHP 8.5.13 changelog lists these security fixes, and each CVE links to its advisory. PHP's changelog doesn't give severity ratings, so check the advisory for details.
CVE-2026-129289 exposure
PHP's advisory says exploitation needs a front end that enables persistent backend connections and an application path that opens php://input without reading it fully. Relevant configurations include nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request aren't affected by the demonstrated attack.
Affected versions are 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13.
CVE-2026-115560 configuration
On 23 October, PHP published an informational advisory for CVE-2026-115560 and said the full advisory would follow with the next regular release. The 19 November releases are that release. An application is only exposed to CVE-2026-115560 if both of these conditions hold:
- Its configuration sets
session.serialize_handlertophp_binaryorphp_serialize, and its code switches the handler tophpwithini_set()before callingsession_start(). - Session upload progress is enabled, which is PHP's default.
The 21 October releases that fixed PHP2Shell don't include a fix for this issue.
Upgrade PHP
Upgrade to the fixed version for your branch. Source and Windows downloads are on the PHP downloads page.
Use Aikido Images
Aikido Images for PHP already include the fixes from the 19 November releases, and we're adding more images. Aikido users can get them from Aikido Images. Everyone else can pull them from the public ECR gallery.
Why do the tags still show the previous version number? We backport security fixes into our images instead of bumping to the upstream release, so the tag keeps its original version number (for example 8.5.12) while the image contains the 19 November fixes. You don't need to wait for an 8.5.13 tag.
Mitigate until you've upgraded
CVE-2026-129289: Turn off backend connection reuse on your front end (the settings listed above), or configure it to close the connection after every request. Reading php://input to the end isn't a reliable fix on its own, because PHP says error paths, resource exhaustion and application shutdown can still leave bytes unread. Don't expose PHP-FPM or LSAPI listeners directly to untrusted networks.
CVE-2026-115560:
- Set
session.upload_progress.enabled=0. PHP's October guidance for this setting says to apply it inphp.ini, an FPM pool or your server configuration.- The guidance says the setting has to apply before request parsing, so don't use
ini_set()or an FPM.user.inifile to change it. - If you already applied it as a mitigation for CVE-2026-109619 in October, keep it in place.
- The guidance says the setting has to apply before request parsing, so don't use
- Restart every PHP worker so the setting takes effect.
- Search your code for runtime calls that switch
session.serialize_handlertophp. PHP says applications that never change the serialize handler at runtime can keep session upload progress enabled.
If you haven't patched PHP2Shell yet
CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell, are a separate pair of critical vulnerabilities that PHP fixed on 21 October in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The 19 November releases include those fixes, so upgrading to the versions above covers both. Our PHP2Shell post has the details.



