On 19 November 2026, the PHP project released versions 8.5.13, 8.4.28, 8.3.37 and 8.2.36, which fix seven flaws rated critical, all scored 9.2 out of 10, including one dubbed phpAfterShell (CVE-2026-126714). Two of them are variants of PHP2Shell, the flaw that required an emergency patch in October. No exploitation had been reported at the time of release, but every branch still maintained is affected by part of the batch.
A fix announced the day before, a month after PHP2Shell
The language team had warned on 18 November, on php.net, that a critical security update would affect all maintained branches, specifying that the most serious flaws require a non-standard or uncommon configuration. It arrived the next day, the same day as the release of PHP 8.6.0, the new major version. The timing echoes that of October: on 21 October, PHP had urgently fixed CVE-2026-109618 and CVE-2026-109619, two flaws allowing unauthenticated remote code execution, and php.net then stressed that only updating removed the risk.
These two October flaws are listed in the US agency CISA’s catalogue of exploited vulnerabilities, IT-Connect recalls. Yet two of the new CVEs, CVE-2026-129481 and CVE-2026-129182, reuse the mechanism of CVE-2026-109619 through paths that the October patch did not cover. In other words, servers updated in October may remain exposed if they do not install the 19 November release.
phpAfterShell: a half-rewritten session
The most publicised flaw was discovered by the company depthfirst, which reported it in late October according to IT-Connect. It affects applications that store their sessions as files on the server. If the writing of a session file is interrupted at the wrong moment, that file can mix the beginning of the new data with the end of the old data. By carefully choosing what they send, an attacker can get these leftovers interpreted as objects, which will be deserialised on the next call to the session start function, The Hacker News explains.
The attack is not trivial: it requires the attacker to be able to influence session data, trigger the interruption at the right moment and find an exploitable object chain in the application. Depthfirst nevertheless claims that by combining it with another of its findings, it leads directly to remote code execution, and the outlet publishes an animated demonstration. Sessions stored in Redis or in a database are not affected, IT-Connect specifies.
The other flaws in the batch
According to IT-Connect, PHP 8.5.13 fixes 18 flaws in total and PHP 8.2.36 fixes 12. The seven critical ones do not affect every branch: all seven target PHP 8.5, five concern PHP 8.4 and 8.3, and four PHP 8.2. The main ones:
- CVE-2026-129289: request smuggling targeting PHP-FPM, which makes it possible to slip a FastCGI request into an HTTP request without authentication; it requires the front-end server to reuse its connections to PHP, as nginx does with fastcgi_keep_conn or Apache with enablereuse;
- CVE-2026-115560: a deserialisation issue linked to the session upload progress feature, already flagged in a PHP advisory on 23 October;
- CVE-2026-129474: a memory management error specific to PHP 8.5, introduced in version 8.5.12;
- CVE-2026-129496: a memory error in the time zone cache, reachable through a crafted request when PHP writes to its log at startup.
The Hacker News also lists an eighth flaw, CVE-2026-129291, scored 8.8, which allows local privilege escalation in certain PHP-FPM configurations.
What to do now
The only complete response is to update to the latest version of your branch: 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Companies that manage their own servers should check their distribution’s packages, and those that are hosted should make sure with their provider that the update has been applied. IT-Connect noted that Debian 13 already offered PHP 8.4.28, while Debian 12’s security tracker still showed a vulnerable version.
In the meantime, three settings reduce exposure, according to IT-Connect:
- disable session upload progress tracking (session.upload_progress.enabled set to 0), which closes the simplest route to phpAfterShell and CVE-2026-115560;
- disable keep-alive of FastCGI connections to PHP on the web server, to guard against CVE-2026-129289;
- on PHP 8.5, disable fatal error backtraces (fatal_error_backtraces set to 0).
After the update, session upload progress tracking is disabled by default unless explicitly enabled. That leaves older versions: PHP 7.4, 8.0 and 8.1 do not appear in the advisories, but the project no longer maintains them, and IT-Connect believes some flaws may affect them, as the PHP-FPM flaw dates back to PHP 5.6. PHP 8.2, for its part, will reach end of life on 31 December 2026, according to php.net: now is a good time to migrate to a more recent branch.
Frequently asked questions
What is phpAfterShell?
It is the nickname of CVE-2026-126714, a PHP flaw related to sessions stored in files. An interrupted write can leave a file mixing old and new data, which an attacker can exploit to inject objects and, under certain conditions, execute code.
Which PHP versions should be installed?
Those released on 19 November 2026: 8.5.13, 8.4.28, 8.3.37 or 8.2.36, depending on the branch used. PHP 8.6.0, released the same day, also includes these fixes. Versions 8.1 and earlier no longer receive patches.
Are these flaws already being exploited?
No exploitation had been reported at the time of release. Caution is still advised: the October PHP2Shell flaws, of which two of the new CVEs are variants, were added to the US catalogue of exploited vulnerabilities.
Sources
- phpAfterShell : PHP corrige 7 failles critiques, dont 2 variantes de PHP2Shell — IT-Connect, 2026-11-19
- PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution — The Hacker News, 2026-11-19
- PHP 8.6.0 Released ; PHP 8.5.13, 8.4.28, 8.3.37 et 8.2.36 (annonces du projet) — php.net (PHP project), 2026-11-19
- PHP 8 ChangeLog : version 8.5.13 (liste des CVE corrigées) — php.net (PHP project), 2026-11-19