Samuel Arendt

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix flaws in sessions, PHP-FPM and PHP-CGI

On November 19, 2026, at 14:00 UTC, PHP released versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36. These are the security releases the project announced the day before without details, which I covered in this morning's advance notice. The ChangeLog now lists the flaws: 17 security advisories in 8.5, 14 in 8.4, 13 in 8.3 and 12 in 8.2.

What landed in all four branches

Three flaws that the ChangeLog describes as able to lead to remote code execution appear in every supported branch:

  • CVE-2026-129496: use-after-free in the timezone cache of the date extension, which is compiled into every installation;
  • CVE-2026-126714: partially overwritten session files;
  • CVE-2026-115560: session serializer mismatch. This is the case PHP described in October, when it recommended turning off session.upload_progress.enabled for applications that switch session.serialize_handler with ini_set() before session_start().

PHP-FPM gets three fixes in every branch: request smuggling when the HTTP request body is left unread (CVE-2026-129289), XSS on the FPM status page (CVE-2026-129292) and an epoll flaw that allows local privilege escalation (CVE-2026-129291). Every branch also gets fixes for an out-of-bounds read and write in PHP-CGI while correcting PATH_INFO (CVE-2026-129538), an OpenSSL signature check bypass in Phar archives (CVE-2026-128090), two flaws in the SOAP extension, HTTPS and FTPS URLs with mixed-case schemes that could travel unencrypted (CVE-2026-128064) and a denial of service through folded HTTP headers (CVE-2026-127960).

The newer branches get extra fixes. 8.3, 8.4 and 8.5 fix a use-after-free after an interrupted session shutdown (CVE-2026-129481), and 8.4 and 8.5 fix a double free in DOM XML serialization (CVE-2026-129501). Only 8.5.13 has another flaw that can lead to remote code execution, in magic method backtraces (CVE-2026-129474), plus a use-after-free after shutdown (CVE-2026-129182) and an error serializing very long URIs (CVE-2026-129438).

Who needs to upgrade

Every team running PHP 8.2, 8.3, 8.4 or 8.5 in production, which includes WordPress, Laravel, Drupal and any application behind PHP-FPM, Apache with mod_php, FrankenPHP or LiteSpeed. The timezone flaw does not depend on an optional extension or a specific setting, so you cannot rule out exposure just by reading php.ini.

Some fixes matter more for people who use specific features. The FPM status page (pm.status_path) is only a problem if it is reachable from outside. PHP-CGI is an uncommon way to run PHP today, but it still shows up on older hosting and on Windows. The Phar flaw matters to anyone who distributes or verifies signed .phar files, such as command-line tools installed that way.

PHP's news feed has no releases for 8.1 or older in this cycle. Teams on those branches depend on their distribution vendor or an extended support contract.

What to do and by when

Upgrade this week, ideally by Friday. The advance notice rated the most severe flaw as critical, and the technical details of all of them are now public.

  • On your own servers using distribution packages or official Docker images, confirm that the package or tag already ships the new version before rebuilding. After upgrading, restart PHP-FPM or Apache; the old process keeps running the vulnerable code until it restarts.
  • On managed hosting, ask the provider whether they apply the upgrade themselves and how quickly.
  • Until the upgrade lands, keep session.upload_progress.enabled=0 if the application switches the session serializer at runtime, and block outside access to the FPM status page.

The 8.2 branch stops receiving fixes on December 31, 2026. Teams on it apply 8.2.36 now and need a plan to leave the branch within six weeks. That is the situation I described in a supported version still calls for a migration decision: the support that remains is too short to start the migration at the last minute.

What is still unknown

The ChangeLog does not give the severity of each flaw or say which ones require the "non-default configuration" mentioned in the advance notice; that rating lives in the security advisories of the php-src repository. PHP has not said whether any of the flaws is already being exploited. It is also unclear when each Linux distribution and hosting provider will ship the patched packages, and whether PHP 8.6.0, planned for the same date, ships with all of these fixes.

If your company is weighing something similar, reach me on LinkedIn or WhatsApp.

References

Closed corrugated metal door with a handle in the center and a circular reflection of light on the panels

Photo by Franck V. on Unsplash

#Operations, #Radar, #Software Quality