The session flaw PHP flagged in October reaches further than one application changing its own settings. According to the advisory published with today’s releases, CVE-2026-115560 can also arise between separate applications, PHP-FPM pools or virtual hosts that access the same session data but use different serializer settings. Separate FPM pools do not automatically get separate session storage. PHP rates the flaw critical.

It is one of seven such fixes in PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, releases that together fix 17 vulnerabilities covered by PHP’s own security advisories: 7 rated critical, 4 high and 6 medium. PHP 8.5.13 also updates the bundled uriparser library for CVE-2026-48841.

Session Upload Progress Is Now Off by Default

Session upload progress, the feature PHP advised administrators to switch off in October, is now disabled by default as part of the fix for CVE-2026-115560. The fix also rejects runtime changes to session settings, including session.serialize_handler, while upload progress is enabled. An explicit setting overrides the new default, so servers that enable the feature in their configuration keep it.

Where upload progress stays enabled, the advisory is explicit: every application reading or writing the same session data must use the same serializer, even after the update. The fix does not enforce this across separate configurations.

7 Critical Fixes and What They Require

All 7 carry a CVSS 4.0 score of 9.2, and each depends on specific conditions, as PHP’s advance notice indicated. Two of them, CVE-2026-129182 and CVE-2026-129481, extend the fixes PHP shipped on October 21 for CVE-2026-109619, one of the two PHP2Shell flaws. For these two, PHP has not demonstrated code execution.

CVEAreaBranchesCondition
CVE-2026-129289PHP-FPM8.2 to 8.5A front end that reuses FastCGI connections and an application that opens the request body stream, php://input, without reading it fully
CVE-2026-115560Sessions8.2 to 8.5Upload progress enabled, session data shared across incompatible serializers and, for code execution, a suitable gadget chain in the reading application
CVE-2026-126714Sessions (files handler, the default)8.2 to 8.5An interrupted session write, attacker influence over session data and a suitable gadget chain in the application
CVE-2026-129496Date8.2 to 8.5A startup warning written to a PHP error log file, such as one for an invalid date.timezone, then an early request warning in a fresh worker
CVE-2026-129474Engine8.5fatal_error_backtraces=1, the 8.5 default, together with zend.exception_ignore_args=0
CVE-2026-129182Engine8.5A fatal error while PHP restores memory-limit or zlib output settings at shutdown
CVE-2026-129481Sessions8.3 to 8.5A fatal error in a callback during session cleanup

For the PHP-FPM flaw, affected front ends include nginx with fastcgi_keep_conn on, as well as Apache’s FastCGI proxy with enablereuse=on. LSAPI shares the underlying cleanup error, which can disrupt later requests on the same connection, but the advisory does not establish code execution through it. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated attack.

For CVE-2026-129474, PHP’s production configuration template, php.ini-production, sets zend.exception_ignore_args=1, which prevents the attack path.

A PHP-FPM Flaw Can Lead From a Pool User to Root

One of the four high-rated fixes, CVE-2026-129291, concerns the PHP-FPM master process. The attacker needs to run PHP code in an FPM worker, for example through their own account on a shared server. From there, they can execute commands with the privileges of the FPM master, which commonly runs as root. If the master runs as an unprivileged user, the attacker gains only that user’s privileges. Exploitation requires, among other conditions, the epoll event backend and a pool that captures worker output, the setting catch_workers_output. Until the update is installed, PHP’s workaround is to disable that setting in affected pools.

Plesk Planned Builds for the Same Versions

Plesk’s community manager listed the same four version numbers on the company’s forum before the release, with Plesk’s builds to follow soon after PHP’s. On Linux, Plesk also plans to backport the fixes to PHP 8.1, 8.0 and 7.4, branches the PHP project no longer updates. A separate update is planned for the PHP engine that runs the panel itself.