PHP · CVE-2026-115560
PHP session RCE
Patch now if…Only with mixed session serializers. Fixed 19 Nov.
PHP's session upload-progress feature can let an attacker with no login run code, but only where sessions are written with one serializer and read with another, and the app has a suitable code library. PHP rates it Critical; exploit code for a test lab is public, and the 19 Nov 2026 releases fix it. It's a sibling of PHP2Shell (CVE-2026-109618/109619).
How scary is it?
Are you affected? only if all are true
1PHP older than the 19 Nov 2026 fixcommand
PHP 8.2 to 8.5 below 8.5.13, 8.4.28, 8.3.37 or 8.2.36. PHP 8.6.0 (19 Nov) is fixed. The 21 Oct releases didn't fix this bug. Older, unsupported PHP may also be affected. Distros may backport the fix without changing the version number.1,2,7
php -v2Session upload progress is oncommand
In anything that can write to your session store. It was on by default before the fix; the fix turns it off by default, but an explicit setting in php.ini or a pool still wins. The CLI can read a different php.ini than PHP-FPM or Apache.1,4
php -i | grep session.upload_progress.enabled3Two serializers share sessionscommand
Something writes sessions with php_binary or php_serialize while something else reads the same sessions with php. For example, an app calls ini_set() before session_start(), or two apps, FPM pools, virtual hosts or CLI jobs with different settings share a session directory. PHP's 23 Oct notice described only the first case; the 19 Nov advisory says no runtime switch is needed.1,3
php -i | grep session.serialize_handler4The reader has a usable library
Code execution needs a suitable "gadget chain" in the reading app. PHP's advisory demonstrates it with Guzzle and Monolog, both common in Composer apps. Without one, the bug can still corrupt sessions or crash requests.1
What to do
1Update PHP and restart
Update to 8.6.0, 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (19 Nov 2026), then restart every PHP worker. Debian has fixed packages (DSA-6641-1, DLA-4916-1); Ubuntu hadn't shipped one by 20 Nov. The fix turns session upload progress off by default and blocks runtime changes to session settings while it's on.1,2,7,9,10
Latest safe versions checked 20 Nov
2Keep upload progress offcommand
Set it in php.ini, the FPM pool or server config, not with ini_set() (that's too late), then restart. Check that nothing explicitly turns it back on.1,4
session.upload_progress.enabled = 03If you need upload progress
Every app, pool and job that reads those sessions must use the same serialize_handler, even after updating. Otherwise give each app its own session storage, and expire old sessions when you change formats.1
This page shows you how to check. It can't tell you you're safe.
Sources (10) and changelog
- PHP GHSA-658j: full advisory, conditions, demonstrated exploit 19 Nov
- PHP: 8.x ChangeLog, 19 Nov 2026 releases 19 Nov
- PHP: 23 Oct notice (described only the runtime-switch case) 23 Oct
- PHP manual: session setting defaults
- BleepingComputer: mitigation, no attacks reported
- CISA KEV catalog: not listed
- PHP: 8.6.0 ChangeLog, fixes GHSA-658j 19 Nov
- Public exploit for a test lab (planted gadget class) 19 Nov
- Debian tracker: DSA-6641-1, DLA-4916-1
- Ubuntu: CVE tracker, needs triage
- PHP 8.6.0 added. A public exploit for a test lab is out (uses a planted gadget class): exploit status set to public. Debian packages out. Safe versions added.
- Rewritten after PHP's full advisory: no runtime switch needed, exploit demonstrated, verdict raised to Patch now if…
- PHP released the fix: 8.5.13, 8.4.28, 8.3.37 or 8.2.36.
- Published.