Home / Blog / PHP security updates fix 18 flaws, including critical RCE…
Tech News

PHP security updates fix 18 flaws, including critical RCE bugs

The PHP team released security updates across four branches to fix 18 flaws, including a critical 9.2 CVSS request smuggling bug enabling remote code execution.

By Dillip Chowdary • Nov 19, 2026 • Source: BleepingComputer

PHP security updates fix 18 flaws, including critical RCE bugs
Image: BleepingComputer

At a glance

Product
PHP
Supported versions
8.5.13, 8.4.28, 8.3.37, 8.2.36
Release date
Thursday, November 19, 2026
Total vulnerabilities
18 CVEs
Critical CVSS
9.2 (CVE-2026-129289)
Legacy backports
PHP 5.6 through 8.1

The PHP development team released coordinated security updates addressing eighteen vulnerabilities across all supported branches of the language runtime. According to BleepingComputer's report, the Thursday release delivers official patches for PHP 8.5.13, PHP 8.4.28, PHP 8.3.37, and PHP 8.2.36. The maintenance rollout resolves critical flaws that could permit unauthenticated remote attackers to execute code on vulnerable servers.

This technical report details the eighteen disclosed vulnerabilities, the affected runtime environments, immediate configuration mitigations, and third-party legacy package releases. It is written for systems engineers, DevOps teams, and web infrastructure administrators operating PHP services in production environments. Readers will find the necessary technical details to protect application listeners and backend processors from unauthorized exploitation.

01Eighteen vulnerabilities across four supported branches

Security firm Aikido confirmed that the eighteen Common Vulnerabilities and Exposures impact multiple subsystems within the runtime architecture. The vulnerabilities span the PHP core engine, session handling mechanisms, PHP-FPM process managers, CGI components, and standard wrappers. Because these flaws touch critical functional layers, operators running diverse server workloads must evaluate their exposure immediately.

The coordinated update follows an alert issued Wednesday by the PHP security team advising operators of pending security fixes. Maintainers warned that the issues rated critical require either non-default configuration or uncommon server setups to be leveraged. Despite those prerequisites, custom production environments across the internet often run architectures that fulfill the vulnerable conditions.

Beyond high-profile execution bugs, the update addresses several lower-severity security flaws documented across the codebase. Patches remediate memory corruption, information disclosure, cross-site scripting weaknesses, and denial-of-service conditions. Core maintainers also resolved vulnerabilities tied to the potentially unsafe handling of HTTPS and FTPS URLs.

02Critical request smuggling in PHP-FPM

The most severe vulnerability resolved in the release cycle is tracked as CVE-2026-129289, carrying a CVSS score of 9.2. Security researchers at Aikido reported that this critical PHP-FPM request smuggling vulnerability permits unauthenticated attackers to execute PHP code remotely. The issue emerges on vulnerable servers that reuse backend connections to PHP-FPM under specific operational conditions.

The flaw specifically affects certain nginx, Apache, HAProxy, and LSAPI server configurations that reuse backend connections to PHP-FPM. In these environments, connection pooling allows an attacker to desynchronize requests and poison the fastcgi execution channel. Web applications deployed on custom proxy setups that keep upstream connections alive face direct exposure to this attack.

Standard web server architectures remain shielded from this exploit path when backend connections are not shared across separate requests. Standard nginx and Apache configurations that do not reuse backend connections are not affected by the attack. Administrators can verify their configuration files to ensure proxy modules close backend sockets promptly after servicing each HTTP transaction.

03Core memory corruption and session execution bugs

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Multiple additional vulnerabilities patched in the update could permit attackers to achieve remote code execution through memory corruption. CVE-2026-129474 fixes a use-after-free vulnerability involving magic method backtraces that could lead to remote code execution. Similarly, CVE-2026-129496 resolves a timezone cache use-after-free defect that allows arbitrary code execution on target hosts.

Session handling mechanisms also contained critical flaws that exposed applications to arbitrary remote execution. CVE-2026-126714 resolves a vulnerability involving partially overwritten session files that could lead to remote code execution. Furthermore, CVE-2026-115560 repairs a session serializer mismatch bug previously disclosed in an October 23 informational advisory that similarly enables code execution.

The update batch incorporates fixes for local privilege escalation and archive verification bypasses. CVE-2026-129291 addresses a PHP-FPM epoll use-after-free vulnerability that could allow local users to elevate privileges. Additionally, CVE-2026-128090 resolves a PHAR OpenSSL signature bypass flaw where an algorithm downgrade allowed attackers to circumvent cryptographic validation checks.

04Temporary worker mitigations and connection settings

Administrators unable to deploy package upgrades immediately can apply configuration workarounds to neutralize specific attack vectors. For CVE-2026-115560, the PHP team recommended disabling session upload progress by setting session.upload_progress.enabled=0 in configuration files and restarting PHP workers. This exact configuration adjustment was previously recommended to mitigate the recent PHP2Shell vulnerabilities across web clusters.

For the critical request smuggling flaw tracked as CVE-2026-129289, administrators can protect unpatched systems by modifying web server proxy behavior. Disabling persistent backend connections between web servers and PHP-FPM ensures that connections are closed after each request. Enforcing connection teardown prevents request pipeline desynchronization until system administrators can execute comprehensive runtime upgrades.

Aikido warns that these configuration mitigations do not address all eighteen vulnerabilities fixed in the November updates. The security firm recommends ensuring that PHP-FPM and LSAPI listeners are never directly exposed to untrusted networks. Network-level access controls and firewall policies must isolate application daemons from public interfaces while patch deployment proceeds.

05Backported legacy packages and upgrade paths

The PHP development team released official security updates exclusively for actively supported runtime branches. Server administrators should upgrade production environments to PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36, depending on their active branch, to remediate all disclosed vulnerabilities. Standard package management workflows provide the quickest path to applying these validated upstream releases.

Note: Although official security updates are limited to supported PHP branches, third-party maintainer Ondrej Surý released patched packages for unsupported PHP versions dating back to PHP 5.6. These community builds provide backward-compatible security remediation for organizations maintaining older application workloads that cannot be immediately migrated to modern runtime versions.

Security firm Aikido also published hardened PHP container images containing backported security fixes for multiple unsupported releases. These hardened container images deliver backported patches for PHP 5.6, 7.0, 7.1, 7.2, 7.4, and 8.1. Infrastructure teams can deploy these remediated container images or install patched packages to protect legacy deployments against active exploitation.

Frequently asked questions

Which PHP branches received official security updates?

The PHP development team released updates for supported branches, making PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36 available. Third-party packages and container images also provide backported fixes for unsupported versions back to PHP 5.6.

What is the most severe flaw fixed in the November updates?

The most critical vulnerability is CVE-2026-129289, a PHP-FPM request smuggling bug with a CVSS score of 9.2. It allows unauthenticated attackers to execute PHP code remotely on servers that reuse backend connections to PHP-FPM.

Are default nginx and Apache setups vulnerable to the critical request smuggling flaw?

No, standard nginx and Apache configurations that do not reuse backend connections are not affected. The vulnerability only impacts configurations reusing backend connections to PHP-FPM under certain conditions.

What temporary mitigation can administrators use for session-based flaws?

Administrators can set session.upload_progress.enabled=0 and restart PHP workers to mitigate the CVE-2026-115560 serializer mismatch flaw. For CVE-2026-129289, administrators should disable persistent backend connections between web servers and PHP-FPM.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →