Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 3 min · 629 words
- Severity
- Routine
PHP patches 18 flaws including critical 9.2-rated RCE bug
PHP's November 19 update fixes 18 CVEs, including a 9.2-rated PHP-FPM request smuggling flaw enabling unauthenticated RCE on nginx, Apache, HAProxy and LSAPI setups with connection reuse.

Event log
- PHP released fixes for 18 CVEs on November 19 across versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36.
- CVE-2026-129289, a PHP-FPM request smuggling flaw rated CVSS 9.2, enables unauthenticated remote code execution.
- Five of the patched CVEs are remote code execution paths; one, CVE-2026-115560, had been public since October 23.
- Third-party patched packages exist for unsupported PHP versions back to 5.6, from Ondrej Surý and Aikido.
PHP shipped fixes for 18 vulnerabilities on Thursday, November 19, with the worst carrying a CVSS score of 9.2. The critical flaw, CVE-2026-129289, allows unauthenticated attackers to remotely execute PHP code on servers that reuse connections to PHP-FPM.
The updates cover every supported branch: PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36. Security firm Aikido reports the patches address 18 CVEs across the core engine, session handling, PHP-FPM, CGI, and other components.
Which configurations are exposed?
The flagship vulnerability is a request smuggling bug in PHP-FPM. It affects certain nginx, Apache, HAProxy, and LSAPI configurations that reuse backend connections to PHP-FPM. Standard nginx and Apache setups that close connections after each request are not affected.
Aikido's assessment carries a caveat worth noting. Exploitation requires "certain conditions," and the PHP security team itself said the critical issues "require either non-default configuration or uncommon setups." In other words, default installs face lower risk than the 9.2 score suggests — but connection-reusing proxies, common in high-traffic deployments, sit squarely in the blast radius.
What else got fixed?
Six additional CVEs stand out in the release. Five of them could lead to remote code execution.
- CVE-2026-129474 — use-after-free in magic method backtraces, leading to RCE.
- CVE-2026-129496 — timezone cache use-after-free, leading to RCE.
- CVE-2026-126714 — partially overwritten session files, leading to RCE.
- CVE-2026-115560 — session serializer mismatch, leading to RCE.
- CVE-2026-129291 — PHP-FPM epoll use-after-free, leading to local privilege escalation.
- CVE-2026-128090 — PHAR OpenSSL signature bypass via algorithm downgrade.
Further fixes cover memory corruption, information disclosure, cross-site scripting, denial-of-service, and what PHP describes as potentially unsafe handling of HTTPS and FTPS URLs. That last phrase is vague. The advisories do not spell out the exact failure mode.
Was any of this known before?
One flaw was already public. CVE-2026-115560 appeared in an October 23 informational advisory. It concerns how PHP handles session data under certain configurations and can end in remote code execution. A vulnerability disclosed three weeks before its patch ships is a working window for attackers, not a theoretical one.
The Wednesday warning from the PHP security team previewed the release but withheld identifiers. That gave administrators one day to plan patching across fleets.
What can admins who cannot patch immediately do?
PHP recommends two temporary mitigations. For CVE-2026-115560, disable session upload progress by setting session.upload_progress.enabled=0 and restart PHP workers — the same setting recommended against 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.
Aikido cautions these workarounds do not cover all 18 vulnerabilities. The firm also recommends ensuring PHP-FPM and LSAPI listeners are never directly exposed to untrusted networks. A mitigation that stops one bug while leaving seventeen open is triage, not a fix.
What about unsupported PHP versions?
Official patches stop at supported branches. Third-party maintainer Ondrej Surý has released patched packages for unsupported versions dating back to PHP 5.6. Aikido has published hardened container images with backported fixes for PHP 5.6, 7.0, 7.1, 7.2, 7.4, and 8.1.
Legacy estates running EOL branches now have options. Note that third-party backports carry their own supply-chain considerations, and neither Surý's packages nor Aikido's images carry the PHP project's own release guarantee.
The bottom line: administrators should upgrade to PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36, matching their branch. Eighteen CVEs, five RCE paths, and one already-public flaw make this a patch-now release.
via bleepingcomputer.com (Source)
More from Daniel Okafor
Show full bio
Staff writer covering technology and product news in enterprise information technology and the leaders who run at CIO Monitor.
205 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- Drupal Patches Critical RCE Flaw Exploitable by Anonymous Users
- NGINX2Root flaws expose 8.8 million servers to root takeover
- PHP2Shell Campaign Wiped VMware ESXi Hosts via Check Point Gateways
- Microsoft's October Patch Tuesday Ships 1,408 CVEs, One Actively Exploited
- Five critical Nginx flaws patched after Linux root exploit chain