The PHP Foundation has released security updates addressing 18 distinct vulnerabilities across multiple supported versions of the language. This batch of patches, released on November 19, 2026, follows a period of heightened security activity for the platform, occurring only one month after the disclosure of two critical flaws collectively referred to as PHP2Shell. While these newly disclosed issues affect all currently supported versions of PHP, the foundation noted that successful exploitation generally requires non-standard configurations or specific, uncommon environmental setups.
Among the most significant of these vulnerabilities is CVE-2026-126714, identified as PHPAfterShell. Discovered by the security firm Depthfirst using artificial intelligence models, this critical flaw resides in the default file-based session handling mechanism. An attacker can manipulate session data during file uploads to potentially trigger arbitrary code execution. If exploited, this vulnerability could grant unauthorized access to sensitive information, such as login credentials and customer records, or allow attackers to disrupt services and monitor user activity. This flaw impacts PHP versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36.
The November update also addresses several other high-severity issues, including four distinct use-after-free vulnerabilities—tracked as CVE-2026-129481, CVE-2026-129474, CVE-2026-129182, and CVE-2026-129496—all of which carry a CVSS score of 9.2 and carry the potential for remote code execution. Additionally, CVE-2026-129289, a request-smuggling vulnerability, poses a significant risk by allowing attackers to manipulate how HTTP request bodies are processed.
Other vulnerabilities addressed in this release include a variety of memory corruption and service disruption risks. CVE-2026-129501 involves a double-free flaw during DOM XML serialization, while CVE-2026-129538 concerns an out-of-bounds read and write issue within PHP-CGI. The update also mitigates a local privilege escalation risk in PHP-FPM’s epoll event handling (CVE-2026-129291) and a cross-site scripting (XSS) vulnerability in the PHP-FPM status endpoint (CVE-2026-129292). Furthermore, an OpenSSL signature verification bypass (CVE-2026-128090) could allow malicious PHAR archives to circumvent security checks.
The release further includes fixes for information disclosure via SOAP processing (CVE-2026-15353), memory corruption during DTD entity reference processing (CVE-2026-129506), and a plaintext transmission risk involving mixed-case HTTPS and FTPS URLs (CVE-2026-128064). A denial-of-service vulnerability related to folded HTTP response headers (CVE-2026-127960) and an URI serialization issue (CVE-2026-129438) were also corrected, alongside a vulnerability in the third-party uriparser library, which was resolved by updating the dependency to version 1.0.3.
These patches arrive in the wake of the PHP2Shell incident, which saw real-world exploitation attempts against internet-facing systems. Security researchers documented campaigns that utilized these earlier flaws to deploy backdoors and target infrastructure, including VMware ESXi virtualization servers and Palo Alto Networks firewalls. The PHP Foundation emphasized that while the latest vulnerabilities require specific conditions for exploitation, the recent history of active attacks underscores the necessity of maintaining updated software.
In response to the release, maintainers of various PHP-based ecosystem projects have initiated efforts to integrate these fixes into their distributions. Projects such as FrankenPHP and the Laravel framework have confirmed they are working to provide updated builds and remediation plans to protect downstream users. These updates are being distributed through various channels, including static binaries, RPM and DEB packages, Homebrew, and container images based on Debian and Alpine Linux.
Users are encouraged to upgrade to the latest versions—8.2.36, 8.3.37, 8.4.28, 8.5.13, or 8.6—to mitigate these risks. The PHP Foundation maintains that versions prior to 8.1 are considered end-of-life and are not covered by these security updates.



