The PHP security team announced on November 18, 2026 that it will publish new security releases this Thursday, November 19, between 14:00 and 14:30 UTC. The fixes cover every supported version, and the highest severity among the issues is critical. The notice gives no version numbers or CVEs: those details come out with the packages.
What the notice says and what it leaves out
The release is part of PHP's regular four-week cycle, the same one that shipped 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21. The last advance notice of this kind came out on October 20, one day before the releases that fixed two unauthenticated remote code execution flaws (an attacker without a login could run code on the server).
The notice carries an important caveat: the issues rated critical "require either non-default configuration or uncommon setups." That lowers the odds that a typical installation is exposed to the worst case, but the notice does not say which configurations those are. Until the release, nobody outside the project can confirm whether a given server is affected.
One of the issues is probably already known. On October 23, PHP recommended turning off session.upload_progress.enabled because of an unlikely remote code execution path. It only occurs when an application sets session.serialize_handler to php_binary or php_serialize and switches it to php with ini_set() before calling session_start(). The project said it would publish the full advisory, as CVE-2026-115560, "with the next release." That release is today's.
Who needs to act
Any team running PHP in production on the 8.2, 8.3, 8.4 or 8.5 branches. That includes WordPress, Laravel, Drupal and any application served through PHP-FPM, Apache with mod_php, FrankenPHP or LiteSpeed. The 8.2 branch receives security fixes only and reaches end of support on December 31, 2026, so teams on it will update now and move to another branch within six weeks.
Teams on 8.1 or older do not get a fix from the project. In October, given the severity, the team published minimal backports for 7.4, 8.0 and 8.1; this week's notice does not promise the same. In that case the fix depends on the distribution vendor or on extended support, if there is a contract.
PHP 8.6.0 was also planned for November 19. The security notice does not mention 8.6, and it is not clear whether the stable release ships at the same time.
What to do today
Book an update window for this afternoon or tomorrow, before the details are known. If you rely on distribution packages (Debian, Ubuntu, Red Hat, official Docker images), check when your vendor publishes the fixed build; in October, distributions received the patches in advance. On managed hosting, ask the provider whether it applies the update itself and how quickly.
If the application uses session upload progress and switches the serializer at runtime, apply the October mitigation now: session.upload_progress.enabled=0 in php.ini or in the FPM pool configuration, then restart every worker. If you already did this in October, keep it.
When the release ships, read each CVE advisory before deciding how urgent it is. If one of the critical issues depends on a configuration you use, the update stops being routine maintenance and becomes the day's priority.
What is still unknown
The version numbers, the number of issues, which configurations make the critical issues exploitable, and whether there is active exploitation. It is also unknown whether PHP 8.6.0 ships today with the same fixes. This piece is based on the advance notice; the technical details depend on the advisories published with the release.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.