What is CVE-2026-115560?
CVE-2026-115560 is a flaw in PHP itself that can let an attacker run code on a web server through PHP’s session upload progress feature, the part of PHP that reports how far a file upload has got. PHP fixed it in its security release of 19 November 2026 and rates it Critical, with a CVSS v4.0 score of 9.2.
When one part of a server writes PHP sessions in one format and another part reads the same sessions in a different format, an attacker can slip data in through a file upload that the reading side turns into PHP objects. With a suitable library on the server, that becomes code execution. The researcher who found it, Dvir Sasson of ZEST Security, showed it with two common libraries, Guzzle and Monolog.
It is a different issue from PHP2Shell (CVE-2026-109618 and CVE-2026-109619). The PHP2Shell updates of 21 October, PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, do not fix it.
Am I affected?
A server is only exposed when all three of these are true:
- Something on the server writes sessions with the
php_binaryorphp_serializesession serialize handler (session.serialize_handler). - Something reads the same sessions with the default
phphandler. That happens when a website’s code switches the handler withini_set()before it callssession_start(), or when two websites, PHP-FPM pools or virtual hosts with different handler settings keep their sessions in the same folder. Separate pools do not get separate session folders unless someone sets them up that way. - Session upload progress (
session.upload_progress.enabled) is switched on. It was on by default until this release; the fixed versions switch it off by default.
Most servers use one handler everywhere, so most are not exposed. The switch can sit in a plugin or library as well as in your own code, and on shared hosting an older website on the same account can be the one writing the sessions, so check rather than assume.
What to do now
- Update PHP to 8.2.36, 8.3.37, 8.4.28, 8.5.13 or 8.6.0, then restart PHP-FPM, or PHP in your hosting panel, so every PHP worker runs the new version.
- Look in php.ini, the PHP-FPM pool settings, your virtual hosts and your hosting panel for
session.upload_progress.enabledset toOnor1. A setting written down there still switches it on after the update, and the update does not stop two separately configured websites from disagreeing about the session format. - Unless a website needs upload progress bars, set
session.upload_progress.enabled = 0in php.ini, the pool settings or your hosting panel. Do not useini_set()or.user.ini: they apply too late to help. If a website does need it, make every website and pool that shares its session folder use the same serialize handler, or give them separate session folders.
PHP 8.1 and older get no fix: switching session upload progress off is the only protection there, and moving to a supported PHP version is the real answer. If you already switched it off for PHP2Shell, keep it off.
How Warden checks it
A scan of your website from the outside cannot see this issue: the conditions live in your server’s PHP settings and code. Warden’s malware & server vulnerability check runs a read-only scanner on your own server over SSH, with no root access. It reads the PHP settings, searches your websites’ code, and shows for each condition what it found, whether your server is affected, possibly affected or not affected, and the steps to fix it.
A check you already ran with the current scanner is matched against this issue too. Run a new check after you update PHP.
The rest of this PHP release
PHP published 17 security advisories with this release, 7 of them rated Critical. For most servers the one to look at next is CVE-2026-129289: when nginx keeps its connections to PHP-FPM open (fastcgi_keep_conn on) or Apache reuses them (enablereuse=on), a single request can make PHP-FPM run an attacker’s code, with no login. Standard nginx and Apache settings close the connection after each request and are not exposed to the attack PHP describes. Updating PHP fixes every issue in the release.
What we do not know yet
We have not seen reports that this flaw is being exploited, and the researcher has not published exploit code. We will update this page if that changes.
Sources
- PHP: news and the 19 November 2026 security releasesphp.net
- PHP: 2026 news archive, including the advisory of 23 October 2026php.net
- Aikido: PHP critical security release, 19 November 2026aikido.dev
- PHP: security advisory GHSA-658j-r8rw-q6mx (CVE-2026-115560)github.com
- PHP: ChangeLog for PHP 8 (19 November 2026 releases)php.net
- ZEST Security: PHP2Shell, the third one (CVE-2026-115560)zestsecurity.io
- PHP: security advisory GHSA-qc49-hpvq-g2w6 (CVE-2026-129289, PHP-FPM)github.com
