
The PHP development team issued coordinated security releases on November 19, 2026, resolving 18 vulnerabilities across all actively supported branches, including multiple flaws capable of enabling unauthenticated remote code execution. According to BleepingComputer's report on the PHP security updates, the newly published versions—PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36—correct defects spanning PHP's core engine, PHP-FPM, session management, CGI, and PHAR archive validation. For organizations running web portals, APIs, and enterprise backend services on PHP, the release addresses high-impact execution and privilege-escalation risks while putting proxy-to-worker connection architectures under scrutiny.
Core Announcement Scope and Eighteen-CVE Footprint
The November 19 rollout followed an advance advisory issued on Wednesday by the PHP security team alerting administrators that upcoming patches would affect every supported release line, with the highest severity rated critical. Security firm Aikido reported that the updates resolve 18 distinct CVEs across foundational runtime subsystems rather than peripheral extensions. Alongside remote code execution and local privilege escalation fixes, the patches address memory corruption, cross-site scripting, information disclosure, denial-of-service conditions, and potentially unsafe handling of HTTPS and FTPS URLs.
In its pre-release warning, the PHP security team noted that the critical-rated vulnerabilities require either non-default configurations or uncommon setups. Even with that qualifier, the scope of affected subsystems—core engine execution, PHP-FPM, CGI, PHAR signature verification, and session serializers—carries broad operational weight. Production web fleets frequently tune reverse proxies, persistent worker pools, and session handlers beyond upstream defaults, making configuration-dependent bugs a practical priority for infrastructure defenders.
Request Smuggling and Memory-Safety Architecture
The highest-profile flaw in the cycle is CVE-2026-129289, a PHP-FPM request smuggling vulnerability assigned a CVSS score of 9.2. According to Aikido, the bug permits unauthenticated attackers to execute arbitrary PHP code remotely on servers configured to reuse backend connections to PHP-FPM under specific conditions. The exposure affects certain nginx, Apache, HAProxy, and LSAPI deployments that maintain persistent backend connections to PHP-FPM, whereas standard nginx and Apache configurations that do not reuse backend connections are unaffected.
Several additional CVEs target memory management and session integrity inside the runtime. Three use-after-free defects create execution or escalation exposure: CVE-2026-129474 involves magic method backtraces and could allow remote code execution, CVE-2026-129496 affects the timezone cache with remote code execution risk, and CVE-2026-129291 stems from PHP-FPM epoll handling and could lead to local privilege escalation. Within session management, CVE-2026-126714 involves partially overwritten session files capable of enabling remote code execution, while CVE-2026-115560—previously disclosed in an October 23 informational advisory—is a session serializer mismatch vulnerability that can likewise lead to remote code execution under certain setups. Rounding out the highlighted issues, CVE-2026-128090 introduces a PHAR OpenSSL signature bypass via an algorithm downgrade.
Developer Workflow and Infrastructure Mitigation Impact
For engineering and operations teams, upgrading directly to PHP 8.5.13, 8.4.28, 8.3.37, or 8.2.36 is the definitive remediation path. When staging or regression testing delays immediate binary deployment, administrators can apply two configuration-level mitigations documented in the advisories. To block exploitation of CVE-2026-129289, operators can disable persistent backend connections between nginx, Apache, HAProxy, or LSAPI web servers and PHP-FPM, ensuring that connections close cleanly after every request rather than remaining pooled across requests.
To mitigate CVE-2026-115560, the PHP team pointed to its earlier recommendation to disable session upload progress by setting session.upload_progress.enabled=0 and restarting PHP workers—the same configuration hardening previously advised against PHP2Shell flaws. Aikido additionally recommended verifying network-level boundaries so that PHP-FPM and LSAPI listeners are never directly exposed to untrusted networks, limiting lateral or direct-access attack paths if an edge proxy is bypassed.
Mitigation Limits and Legacy Branch Caveats
Aikido emphasized that temporary configuration changes do not cover all 18 vulnerabilities patched in the November updates. Disabling persistent connections and session upload progress leaves systems exposed to the remaining use-after-free, PHAR signature-downgrade, memory corruption, and URL-handling flaws, meaning workarounds serve only as short-term stopgaps prior to full version upgrades.
Release lifecycle boundaries also create maintenance tradeoffs for organizations operating end-of-life PHP environments. Official upstream patches apply exclusively to PHP 8.2 through 8.5. To support older deployments, third-party maintainer Ondrej Surý released patched packages for unsupported PHP versions dating back to PHP 5.6, while Aikido published hardened PHP container images containing backported security fixes for PHP 5.6, 7.0, 7.1, 7.2, 7.4, and 8.1. Although third-party packages and hardened containers help mitigate immediate risk on legacy stacks, relying on backports outside upstream maintenance reinforces the long-term operational necessity of migrating workloads onto supported PHP branches.
Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-19.



