PHP patches 18 flaws, seven rated critical

The PHP Foundation has released security patches for 18 vulnerabilities, seven of them rated critical, in a security update published on 19 November 2026. The fixes cover every supported branch of PHP, the programming language behind a large share of the world's websites, and the foundation warned users a day earlier that the most serious flaws were critical. The patched versions are 8.2.36, 8.3.37, 8.4.28 and 8.5.13, released alongside PHP 8.6.
The most closely watched flaw is a session-handling weakness dubbed PHPAfterShell, tracked as CVE-2026-126714. Security firm Depthfirst found it using AI frontier models tuned for cybersecurity work. It lives in PHP's session handling with file-based storage, which is the default setting, and an attacker can exploit it by interrupting a session write while a file is being uploaded, leaving a session file that mixes old and new data. That mixed data can trick the server into running arbitrary code, although doing so also needs a suitable gadget chain in the application itself. It affects PHP 8.5 below 8.5.13, 8.4 below 8.4.28, 8.3 below 8.3.37 and 8.2 below 8.2.36. PHP 8.1 and earlier are end of life and receive no fix.
Session flaws dominate the critical list
A second critical flaw, CVE-2026-115560, is a remote code execution weakness in session upload progress, disclosed by PHP on 23 October. When upload progress is enabled, session data can be written in one serialiser format and read back in another, and the mismatch can let an attacker influence objects that PHP later unserialises. Infosecurity Magazine notes that exploiting it needs a highly specific and unlikely combination of conditions.
Four more flaws carry the top CVSS score of 9.2. They are use-after-free weaknesses: CVE-2026-129481, triggered by an interrupted session shutdown; CVE-2026-129474, in magic method backtraces; CVE-2026-129182, in the repopulation of the last fatal error backtrace after shutdown; and CVE-2026-129496, in the time zone cache. Each could allow memory corruption and remote code execution. A seventh critical flaw, CVE-2026-129289, is a PHP-FPM request-smuggling bug: when PHP-FPM reuses backend connections and an application opens the request body without fully reading it, leftover data can be interpreted as a second FastCGI request, letting an unauthenticated attacker run PHP code. The attack needs one request and no memory corruption, but it does need a front end that keeps backend connections open, such as nginx with fastcgi_keep_conn enabled or Apache mod_proxy_fcgi with enablereuse enabled. Semgrep, which analysed the release, counts 17 PHP flaws plus a separate issue in the bundled uriparser library, CVE-2026-48841, making 18 entries in total.
The release also fixes a PHP-FPM privilege escalation flaw, CVE-2026-129291, rated 8.8, an OpenSSL signature verification bypass that could let malicious PHAR archives pass checks, CVE-2026-128090, rated 7.7, and a denial-of-service flaw in folded HTTP response headers, CVE-2026-127960, rated 8.7.
A month after PHP2Shell
The update comes a month after the disclosure of two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell. In the weeks that followed, researchers documented real exploitation attempts against internet-facing systems. Check Point reported campaigns exploiting PHP2Shell against its own security gateways dating back to 30 October, involving backdoors and destructive tools aimed at VMware ESXi servers, and attackers also targeted Palo Alto Networks firewalls whose administrative interfaces were exposed to the internet.
That history is a warning, but the new flaws are not all equally exposed. Infosecurity Magazine notes that the vulnerabilities in the November update affect all supported PHP versions but require either non-default configuration or uncommon setups to be exploited, so administrators should check their own settings rather than assume the worst or the best.
What site owners should do
Site owners should upgrade to the patched version for their branch and restart PHP-FPM or Apache so the new code loads. Anyone still on PHP 8.1 or earlier has no patch to install and should plan a move to a supported branch. Administrators should also check whether session upload progress is enabled and whether their front end reuses FastCGI connections, since those settings decide whether the two most serious flaws are reachable at all.
Projects that build on PHP are already moving. FrankenPHP, a modern PHP application server built around the Caddy web server, said it is working with The PHP Foundation and Docker to provide updated builds, including static binaries, RPM and DEB packages, Homebrew packages and Docker images. Laravel, the widely used PHP framework, said it was already working on a remediation plan to protect applications running across its hosting and deployment services.