TLDR
PHP will ship security releases for all supported versions on 19 November between 14:00 and 14:30 UTC.
The PHP security team rated the most severe issue in the batch as critical.
The release includes a full fix for CVE-2026-115560, a code execution flaw first flagged on 23 October.
The flaw only affects apps that switch their session serialize handler at runtime.
Turning off session upload progress blocks the flaw until the patch is installed.
PHP is set to ship security releases for all supported versions on Thursday, 19 November 2026. The updates are scheduled to go out between 14:00 and 14:30 UTC. One of the flaws in the batch was first flagged by the PHP team almost a month ago.
The PHP security team announced the releases on 18 November. It rated the most severe issue in the batch as critical.
PHP said the critical issues only affect installations with non-default settings or uncommon setups. The full list of CVEs and the fixed version numbers have not been published yet.
A Flaw Left Open Since October
One vulnerability expected in the release is already public. It is tracked as CVE-2026-115560 and is a remote code execution vector in session upload progress.
PHP posted an informational advisory about the flaw on 23 October. At the time, it said the full advisory would come with the next regular release. The 19 November releases are that next regular release.
The 21 October releases did not fix this issue. Those earlier updates targeted a separate pair of critical flaws.
PHP has not shared which versions are affected by CVE-2026-115560. It has also not given the flaw a severity score.
View post by @TheHackersNews on X
An application is exposed only if two conditions are both true. First, its configuration sets the session serialize handler to php_binary or php_serialize, and its code switches the handler to php with ini_set() before calling session_start().
Second, session upload progress must be turned on. That is PHP’s default setting, so many servers meet this condition without any changes.
Steps Before the Patch Arrives
Developer security firm Aikido outlined steps for teams to take now, based on PHP’s guidance. The first is to set session.upload_progress.enabled to 0 in php.ini, an FPM pool or the server configuration.
PHP’s October guidance says this setting must apply before request parsing. That means ini_set() or an FPM .user.ini file should not be used to change it. Every PHP worker then needs a restart for the change to take effect.
Teams that already turned off the setting in October to guard against CVE-2026-109619 can leave it in place. PHP said no further action is needed in that case.
Teams are also advised to search their code for runtime calls that switch the serialize handler to php. According to PHP, apps that never change the handler at runtime can keep session upload progress turned on.
The last step is to upgrade to the new releases as soon as they become available.
The earlier pair of flaws, CVE-2026-109618 and CVE-2026-109619, is known together as PHP2Shell. Both were rated critical and were fixed on 21 October.
The PHP2Shell fixes shipped in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Users still on older versions are urged to update now rather than wait for Thursday’s releases.
The new releases are due between 14:00 and 14:30 UTC on 19 November. PHP will publish the full CVE list and the fixed version numbers at the same time.

