PHP Security Update Patches 18 Flaws, Including Seven Critical Remote Code Execution Bugs

PHP has released security updates for every supported branch, fixing 18 vulnerabilities — seven of them rated critical, each with a CVSS score of 9.2. The flaws affect session handling, PHP-FPM and core runtime code, and several can lead to remote code execution. Users should upgrade to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 as soon as possible.

Nov 21, 2026 - 21:43
Nov 21, 2026 - 21:44
 0  2
PHP Security Update Patches 18 Flaws, Including Seven Critical Remote Code Execution Bugs
A developer typing at a dual-monitor workstation, with PHP code open in an editor on the left screen and a PHP website preview on the right screen.

PHP Security Update Patches 18 Flaws, Including Seven Critical Remote Code Execution Bugs

PHP has shipped a major security release fixing 18 vulnerabilities across every supported branch of the language, seven of which are rated critical and can lead to remote code execution. The patches, released on November 19, 2026, cover PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, while PHP 8.6.0, released the same day, carries the same fixes. Anyone running a supported version of PHP should update now.

The release arrives as part of PHP's regular four-week release cycle, and the PHP team warned users a day earlier, on November 18, that the fixes were coming. Seventeen of the 18 flaws sit in PHP itself; the last one is in uriparser, a URI parsing library bundled with PHP, which was fixed by upgrading the dependency to version 1.0.3.

Seven critical flaws, all scored 9.2

All seven critical vulnerabilities carry a CVSS score of 9.2, the top end of the scale. They cluster around three areas of the runtime: session handling, PHP-FPM and core memory management.

The most attention-grabbing is CVE-2026-129289, a request-smuggling flaw in PHP-FPM. It bites when a web server reuses persistent FastCGI connections to PHP-FPM and an application opens the raw request body without reading it to the end. Leftover bytes from one request can then be mistaken for the start of the next, letting an unauthenticated attacker smuggle a crafted request through — and, according to security researchers, achieve remote code execution with a single request in that configuration.

Two of the critical flaws live in PHP's session handling. CVE-2026-126714, dubbed PHPAfterShell and found by security firm Depthfirst, exploits the way session files are written when a file is being uploaded: an interrupted write can splice old and new session data together, and with a suitable object chain in the application that can lead to code execution. It affects the default file-based session storage. The other, CVE-2026-115560, is a session serializer mismatch: when session upload progress is enabled and different parts of a system write and read the same session with different serializers, attacker-influenced data can be turned into program objects. PHP disclosed this one on October 23, and researchers note it cannot be fully fixed by the patch alone — administrators also need to align their session serializer settings.

The remaining four critical flaws are use-after-free bugs: CVE-2026-129481, triggered by an interrupted session shutdown; CVE-2026-129474, in magic method backtraces; CVE-2026-129182, involving the repopulation of the last fatal error backtrace after shutdown; and CVE-2026-129496, in the time zone cache. Each can corrupt memory and potentially allow arbitrary code execution, though researchers note that a working exploit has not been demonstrated for every one of them.

Eleven more flaws, from privilege escalation to plain-text leaks

Beyond the critical seven, the release fixes eleven further vulnerabilities. The most serious is CVE-2026-129291, scored 8.8, a use-after-free flaw in PHP-FPM's epoll event handling that could let someone who can already run PHP code in a worker escalate to the privileges of the FPM master process, often root.

CVE-2026-127960, scored 8.7, is a denial-of-service flaw involving folded HTTP response headers, while CVE-2026-128064, scored 8.2, is a subtler danger: mixed-case HTTPS and FTPS URLs could cause sensitive information to be sent in plain text instead of encrypted. CVE-2026-128090, scored 7.7, is an OpenSSL signature verification bypass caused by an algorithm downgrade, which could let malicious PHAR archives pass signature checks.

The rest are rated medium: a double-free flaw during DOM XML serialization (CVE-2026-129501), an out-of-bounds read and write in PHP-CGI when correcting the PATH_INFO variable (CVE-2026-129538), a cross-site scripting flaw in the PHP-FPM status endpoint (CVE-2026-129292), an information disclosure flaw in SOAP processing (CVE-2026-15353), a use-after-free flaw when processing DTD entity references (CVE-2026-129506) and an incorrect URI serialization flaw affecting oversized input (CVE-2026-129438).

What makes this release different from October's emergency

The November release comes barely a month after PHP's emergency fixes for two critical flaws, CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell. That was not a theoretical risk: in the weeks after disclosure, researchers documented real exploitation attempts against internet-facing systems, including campaigns reported by Check Point against its own security gateways and attacks on Palo Alto Networks firewalls, with backdoors and destructive tools deployed against VMware ESXi servers.

By contrast, no exploitation of the new November flaws has been reported so far. That is no reason to wait, though — the pattern from October shows how quickly public flaws in a runtime used by a huge share of the web attract attention. It is also worth noting that several of the new flaws only trigger under non-default configuration or uncommon setups, which limits exposure for many sites but makes the risk harder to assess without checking.

What to do now

Upgrade to the fixed release for your branch: PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or move to PHP 8.6.0. Then restart PHP-FPM and your web server so the patched code is actually running. PHP 8.1 and earlier versions are end-of-life and receive no fixes, so systems still on those branches need to move to a supported release.

While updating, check the specific conditions that expose each flaw. If your web server reuses persistent FastCGI connections to PHP-FPM, review whether any endpoint reads the request body incompletely. If session upload progress is enabled, review your session serializer settings and consider turning the feature off if you do not need it. Linux distributions have also begun publishing fixed packages, so check your distribution's security updates as well.

Projects built on PHP are already moving. FrankenPHP said it is working with The PHP Foundation and Docker to ship updated builds, including static binaries, RPM and DEB packages, Homebrew packages and Docker images. Laravel said it is already working on a remediation plan for applications across its hosting and deployment services.

The bottom line is simple: this is a large, well-documented security release with working fixes available for every supported branch. Update, restart, and check the settings the advisories call out.

Sources

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0