Security alert · Critical
PHP fixes critical session flaw CVE-2026-115560 and six other code execution bugs
· 6 minutes read · Centoculus Security Team
Known since
Affected: PHP before 8.2.36, 8.3.x before 8.3.37, 8.4.x before 8.4.28, 8.5.x before 8.5.13
What happened
On 19 November 2026 the PHP team released security updates for all supported branches: PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13. According to the security firm Aikido, as reported by BleepingComputer, the releases fix 18 vulnerabilities in the core engine, session handling, PHP-FPM, CGI and other components. Seven of them have a CVSS score of 9.2 and can lead to remote code execution under certain conditions.
This article focuses on CVE-2026-115560, a session serializer mismatch. PHP had already described this issue in an informational advisory on 23 October 2026, together with a temporary mitigation. Disclosure and the fix followed on 19 November.
The flaw works like this. When session upload progress is enabled, an attacker can submit a multipart upload and put data they control into a session key. That data is stored with the php_binary or php_serialize session serializer. If the same session is later read with the php serializer, bytes inside the key can reach the unserializer. This happens when session.serialize_handler is changed at runtime, or when applications that share one session store use different handlers. The attacker can then inject objects. If the reading application contains a suitable gadget chain, this can lead to code execution. Otherwise it can corrupt sessions or cause a denial of service.
The PHP security team said that the issues rated critical need either a non-default configuration or an uncommon setup. There are no reports of attacks so far, and CISA does not list the vulnerability as exploited.
The other critical flaws fixed in the same release:
- CVE-2026-129289: PHP-FPM request smuggling. An unauthenticated attacker can run PHP code if the front end keeps persistent connections to the backend open and the application opens
php://inputwithout reading it fully. Examples: nginx withfastcgi_keep_conn on, Apache mod_proxy_fcgi withenablereuse=on, HAProxy FastCGI setups that keep backend connections open, and LSAPI. Standard nginx and Apache configurations that do not reuse backend connections are not affected. Fixed in 8.2.36, 8.3.37, 8.4.28 and 8.5.13. - CVE-2026-126714: a time-of-check to time-of-use flaw involving partially overwritten session files. It can lead to code execution as the PHP worker. Fixed in 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
- CVE-2026-129496: a use-after-free in the timezone cache. It can let an unauthenticated remote attacker crash PHP workers or run code with their privileges. Fixed in 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
- CVE-2026-129481: a use-after-free in session cleanup. It can corrupt memory, crash a reused PHP worker or possibly allow code execution. Fixed in 8.3.37, 8.4.28 and 8.5.13.
- CVE-2026-129182: a use-after-free that can cause memory corruption and possibly code execution. Fixed in 8.5.13.
- CVE-2026-129474: a use-after-free in backtraces from magic method calls, affecting PHP 8.5 and later. Fixed in 8.5.13.
The release also fixes CVE-2026-129291, a use-after-free in PHP-FPM's epoll handling that can lead to local privilege escalation, and CVE-2026-128090, a bypass of PHAR OpenSSL signatures through an algorithm downgrade. The remaining fixes cover memory corruption, information disclosure, cross-site scripting, denial of service and unsafe handling of HTTPS and FTPS URLs.
Who is affected
CVE-2026-115560 affects PHP versions before 8.2.36, 8.3.x before 8.3.37, 8.4.x before 8.4.28 and 8.5.x before 8.5.13. Exploitation requires all of the following:
- session upload progress is enabled (
session.upload_progress.enabled) - data written with
php_binaryorphp_serializeis later read with thephpserializer, either becausesession.serialize_handleris changed at runtime or because applications sharing one session store use different handlers - for code execution, the reading application contains a usable gadget chain
Servers where all applications use the same serializer for a session store are not exposed to this particular flaw. Because the same release fixes several other critical issues in all supported branches, every server running PHP should still be updated.
Older branches such as 8.1 and earlier no longer receive official updates. According to BleepingComputer, Ondřej Surý has published patched packages for unsupported versions back to PHP 5.6, and Aikido offers hardened container images with backported fixes.
What to do now
- Update PHP to 8.2.36, 8.3.37, 8.4.28 or 8.5.13, depending on your branch. If you use distribution packages, the Sury repository or the PHP builds of a hosting panel, install the security update from that source. Do this for every installed PHP version on the server, as hosting servers often run several.
- Restart PHP-FPM, Apache with mod_php or LSAPI/LiteSpeed so the workers load the new version, for example with
systemctl restart php8.3-fpm. The service name depends on your distribution and version. - If you cannot update right away, disable session upload progress as PHP recommends. Set
session.upload_progress.enabled = 0in php.ini or in the pool configuration, then restart the PHP workers. This mitigation only covers CVE-2026-115560 and not the other flaws. - Until the update is in place, protect against CVE-2026-129289 by disabling persistent backend connections between the web server and PHP-FPM so that connections close after each request. In nginx, remove
fastcgi_keep_conn on. In Apache, removeenablereuse=onfrom mod_proxy_fcgi. - Make sure PHP-FPM and LSAPI listeners are not reachable from untrusted networks. They should listen only on a Unix socket or on localhost.
How to check whether you are affected
- Check the version of each PHP installation with
php -v. For PHP-FPM, also check the version on aphpinfo()page or withphp-fpmX.Y -v. Distributions sometimes ship fixes under their own version numbers, so check your distribution's changelog. - Check the session settings with
php -i | grep -E 'session.upload_progress.enabled|session.serialize_handler'. Also look for overrides in your FPM pool files (php_valueorphp_admin_value),.htaccessand.user.ini. - Search your application code for runtime changes of the serializer, for example with
grep -rn "session.serialize_handler" /var/www. Also check whether several applications with different handlers share one session directory or session store, such as Redis or Memcached. - For CVE-2026-129289, check your web server configuration with
grep -rn 'fastcgi_keep_conn' /etc/nginxandgrep -rn 'enablereuse' /etc/apache2 /etc/httpd.
Update November 20, 2026
Update: The new report carries no CVE ID of its own (internal reference TOPIC-20261119-d1202d33). It is The Hacker News coverage of the PHP maintainers' announcement of the 19 November security release, which fixes critical vulnerabilities in all supported versions. This is the same release described above, and the report adds no new flaws, versions or exploitation details. The steps in this article already cover it: update to PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13 and restart the PHP workers. No additional step is needed.
Update November 20, 2026
Update: More details are now available for CVE-2026-126714, which has been named "phpAfterShell" and has a CVSS score of 9.2. The default files session save handler writes new session data into the existing session file without clearing it first. If a write is interrupted, the file can hold the start of the new session followed by the end of the old one, and an attacker who can influence session data, for example through session upload progress, may inject objects that lead to code execution if the application contains a suitable gadget chain. The update in step 1 (PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13) followed by the restart in step 2 fixes this flaw, and no attacks have been reported. Note that the description names session upload progress only as one example of influencing session data, so disabling it (step 3) should not be treated as a full mitigation for this CVE.
Sources
More sources (8)
- https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx
- https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
- https://thehackernews.com/2026/11/php-fixes-7-critical-flaws-including.html
- https://www.bleepingcomputer.com/news/security/php-security-updates-fix-18-flaws-including-critical-rce-bugs/
- https://www.heise.de/news/PHP-behebt-17-Sicherheitsluecken-vier-erlauben-Ausfuehrung-von-Schadcode-11531249.html
- https://bugzilla.suse.com/show_bug.cgi?id=1290690
- https://depthfirst.com/phpAfterShell
- https://github.com/semgrep/detection-scripts/pull/14
More on PHP
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.