The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

PHP Fixes 7 Critical Flaws, Led by CVE-2026-126714

By The Daily Byte ·21 Nov 2026 ·4 min read
A developer working late at night on a laptop displaying lines of code, with a large monitor behind him

PHP has shipped security releases fixing 18 vulnerabilities, seven of them rated critical, including session-handling flaws that can let an attacker run their own code on a web server. The patches, published on 19 November 2026, cover every supported PHP branch, and the maintainers are urging administrators to upgrade promptly. Fixed versions are PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, alongside the new 8.6.0 release.

The headline flaw is CVE-2026-126714, nicknamed phpAfterShell and rated 9.2 out of 10 on the CVSS scale. It sits in PHP's default file-based session storage, the handler most PHP sites use unless they have deliberately configured something else. When PHP writes updated session data to disk, the write is not atomic, so if it is interrupted the file can end up holding a mixture of old and new data. The next time a session starts, PHP reads that mixture back, and an attacker who can influence session data can shape it so the result is treated as objects of their choosing. Combined with a suitable code path in the application, those objects can turn into remote code execution in the PHP worker.

phpAfterShell: the flaw October's patches missed

The bug was found by security firm Depthfirst, which says it used AI frontier models tuned for cybersecurity work to find it. The firm reported the issue privately in late October, and PHP published the fix on 19 November. That timing matters: the emergency October releases that fixed the two PHP2Shell flaws, CVE-2026-109618 and CVE-2026-109619, do not contain this fix, so servers patched only in October are still exposed. Sites that store sessions in Redis or a database are outside this particular defect, but no framework changes the answer for sites using the default file store.

Until the new build is running, Depthfirst advises switching off session upload progress by setting session.upload_progress.enabled to 0 in php.ini and restarting the PHP workers. That removes the easiest route to the flaw, but it is a temporary mitigation, not a fix. The upgrade itself is still required.

The other flaws to prioritise

Two more critical flaws stand out. CVE-2026-115560 is a remote code execution flaw in session upload progress, disclosed by PHP on 23 October, two days after the PHP2Shell emergency fixes. PHP's maintainers note that exploiting it needs a highly specific and unlikely combination of conditions. CVE-2026-129289 is a request-smuggling flaw in PHP-FPM, the process most Nginx and many Apache sites use to run PHP. When the front end reuses FastCGI connections and an application opens the request body without reading it to the end, a leftover fragment can be treated as a new request. Analysis by Upwind calls it the flaw to close first, because it gives an unauthenticated attacker PHP code execution with a single request, with no memory corruption, gadget chain or race needed.

The remaining four critical flaws, all rated 9.2, are use-after-free bugs that can corrupt memory and in some cases allow code execution: 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. Two of them, CVE-2026-129474 and CVE-2026-129182, affect only PHP 8.5, which introduced the fatal-error backtrace feature they rely on. PHP also notes that the critical issues generally need a non-default configuration or an uncommon setup, which is why security researchers describe this release as serious but not the same level of emergency as last month.

Why patching PHP matters so much

Context explains the urgency. PHP2Shell, disclosed in October, was exploited in the wild within weeks: Check Point reported campaigns 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 with internet-exposed administration interfaces. PHP runs a huge share of the web, and it is often buried inside content management systems, hosting control panels, vendor appliances and old internal applications, so many organisations do not have a complete inventory of where it is running.

That makes the practical advice straightforward. Upgrade PHP to the fixed release for the branch in use, restart PHP-FPM or Apache so old workers go away, and rebuild container images and appliances that bundle their own PHP build. PHP 8.1 and older are end of life and will not receive these fixes, which is one more reason to move off them. Internet-facing PHP systems should go to the front of the patch queue, because attackers have repeatedly shown they will move quickly when a path to code execution exists.