Skip to content
feed: live
0dayNews
php

PHP patches critical RCE flaws in 8.2 through 8.5

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix 18 CVEs, including critical RCE bugs. Here is who is exposed, what to patch first, and the stopgaps.

PHP patches critical RCE flaws in 8.2 through 8.5
Image: AI-generated — conceptual illustration, not incident evidence / 0dayNews AI Cover · Generated on-site infrastructure — no external license
fuseMarisol "Fuse" Delgado·Published ·2 min read

The PHP project shipped security releases on Thursday, November 19: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. BleepingComputer reports the updates address 18 CVEs across the core engine, session handling, PHP-FPM and CGI, citing analysis from Aikido. No source in this coverage reports exploitation in the wild.

What to do first

Upgrade to the fixed release for your branch. That is the only fix that covers everything. The PHP security team said the critical issues need either non-default configuration or uncommon setups, so exposure varies a lot by deployment. Don’t read that as “skip it”: the setups in question are common enough in front-end proxy stacks.

Patch order, based on what the sources describe:

  1. Servers where a web server reuses backend connections to PHP-FPM. CVE-2026-129289 is a request smuggling flaw that The Hacker News and BleepingComputer both rate critical. Affected setups include certain nginx, Apache mod_proxy_fcgi, HAProxy FastCGI and LSAPI configurations. Standard nginx and Apache configurations that do not reuse backend connections are not affected.
  2. Anything using PHP sessions. CVE-2026-115560 (a session serializer mismatch) and CVE-2026-126714 (partially overwritten session files, which Depthfirst has nicknamed “phpAfterShell”) can both lead to remote code execution. The second needs an application with a suitable deserialization gadget chain, per the report.
  3. PHP 8.5 and later, or any build with timezone or magic-method paths in play. CVE-2026-129474 and CVE-2026-129496 are use-after-free bugs that could lead to RCE. The first is limited to PHP 8.5 and later.
  4. Shared hosts running PHP-FPM. CVE-2026-129291 is a local privilege escalation that needs code execution inside an FPM worker plus specific pool settings. It matters most where tenants share a pool.

Stopgaps if you can’t upgrade today

  • For the session flaw, PHP recommends setting session.upload_progress.enabled=0 and restarting PHP workers. The same setting was advised for the recent PHP2Shell flaws.
  • For CVE-2026-129289, disable persistent backend connections between the web server and PHP-FPM so connections close after each request.
  • Keep PHP-FPM and LSAPI listeners off untrusted networks.

Aikido warns these mitigations do not cover every vulnerability in the release. Treat them as a bridge to the upgrade, not a substitute.

Unsupported PHP versions

The official fixes cover only supported branches. BleepingComputer reports that third-party maintainer Ondrej Sury has released patched packages for unsupported versions back to PHP 5.6, and Aikido has published hardened container images with backported fixes for versions including 5.6, 7.0, 7.1, 7.2, 7.4 and 8.1. Those are third-party builds, so vet them like any other dependency. If you are on an end-of-life branch, the real fix is migrating.

Priority call

Proxy-fronted PHP-FPM with connection reuse goes first, session-heavy applications second, everything else in your normal emergency-patch window. The PHP security team had warned the day before that these releases were coming, so expect scanners and write-ups to follow quickly.

Related hub: PHP.

Found this useful? Share it.