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

The Daily Byte

Stories from Pakistan that deserve to be heard

PHP Fixes 18 Flaws Including Critical RCE

By The Daily Byte ·21 Nov 2026 ·4 min read
A laptop displaying PHP source code in a code editor

The PHP development team has released security updates fixing 18 vulnerabilities, including critical flaws that could allow unauthenticated attackers to run code on vulnerable servers. The patches, published on Thursday 19 November, cover every supported PHP branch, with fixed versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36 now available.

Security firm Aikido, which analysed the release, counts 18 CVEs across PHP's core engine, session handling, PHP-FPM, CGI and other components. Infosecurity Magazine reports that seven of the flaws are marked critical. The fixes arrive a month after the disclosure of two critical PHP flaws collectively known as PHP2Shell, and this release is a separate, larger batch of patches.

The flaw that matters most

The most serious flaw in the batch is tracked as CVE-2026-129289, a PHP-FPM request smuggling vulnerability carrying a CVSS score of 9.2. According to Aikido, it allows unauthenticated attackers to execute PHP code remotely on vulnerable servers that reuse connections to PHP-FPM under certain conditions.

The flaw affects certain nginx, Apache, HAProxy and LSAPI configurations that reuse backend connections to PHP-FPM. Standard nginx and Apache configurations that do not reuse backend connections are not affected, BleepingComputer reports.

Administrators who cannot patch immediately can mitigate CVE-2026-129289 by disabling persistent backend connections between their web servers and PHP-FPM, so connections close after each request. Aikido warns that this mitigation does not address all the flaws in the November updates, and recommends keeping PHP-FPM and LSAPI listeners out of reach of untrusted networks.

The PHP security team cautioned that the flaws rated critical "require either non-default configuration or uncommon setups". That limits the immediate exposure for typical installations, but it is not a reason to delay: the affected configurations are common in high-traffic deployments, where PHP-FPM connection reuse is a standard performance choice.

Session handling flaws

Several of the critical flaws sit in PHP's session handling. One, dubbed PHPAfterShell and tracked as CVE-2026-126714, was found by security firm Depthfirst using AI frontier models tuned for cybersecurity work. It involves partially overwritten session files and can lead to remote code execution. It affects file-based session storage, which is PHP's default setting.

Another, CVE-2026-115560, is a session serializer mismatch that can also lead to remote code execution. PHP had already disclosed it in an informational advisory on 23 October. As a temporary mitigation, PHP recommended disabling session upload progress by setting session.upload_progress.enabled to 0 and restarting PHP workers, a setting also recommended against the earlier PHP2Shell flaws.

The remaining fixes include four more use-after-free flaws scored at 9.2 - CVE-2026-129481, CVE-2026-129474, CVE-2026-129182 and CVE-2026-129496 - covering session shutdown, magic method backtraces, fatal error backtraces and the timezone cache. Other patches address a PHP-FPM privilege escalation flaw, CVE-2026-129291, scored 8.8; a denial-of-service flaw, CVE-2026-127960, scored 8.7; a flaw that could send sensitive data in plaintext when HTTPS or FTPS URLs use mixed case, CVE-2026-128064, scored 8.2; and a PHAR signature bypass, CVE-2026-128090, scored 7.7.

What administrators should do

Administrators should upgrade to the fixed release for their branch: 8.5.13, 8.4.28, 8.3.37 or 8.2.36. The PHP team warned users on 18 November that the fixes were coming and urged them to set aside time to upgrade promptly.

There is an extra deadline for sites still on PHP 8.2. That branch stops receiving security fixes on 31 December 2026, so an upgrade to a supported branch is needed within weeks, not months. PHP 8.1 and earlier are already end of life and receive no fixes in this release.

For unsupported versions, third-party maintainer Ondrej Sury has released patched packages going back to PHP 5.6, and Aikido has released hardened container images with backported fixes. Those are stopgaps for systems that cannot move yet; the supported releases are the fix.

Neither report describes exploitation of the 18 newly patched flaws in the wild. That is the window administrators have: patch while it is still only a disclosure, because the history of PHP2Shell shows that exploitation of critical PHP flaws can follow quickly once details are public.