# phpAfterShell (CVE-2026-126714): Live PHP RCE Updates
_Source: https://www.precursorsecurity.com/blog/phpaftershell-critical-php-rce-vulnerabilities_

[Intelligence Library](/blog)

Threat IntelligenceLive

# phpAfterShell and the November PHP Security Release (7 Critical CVEs)

PHP's 19 November release fixes 17 vulnerabilities, seven of them critical, including phpAfterShell and a PHP-FPM request smuggling flaw that can run attacker code without logging in. We are tracking developments as they happen.

phpAfterShell (CVE-2026-126714, CVSS 9.2) is a critical flaw in PHP's default file session handler, fixed on 19 November 2026 alongside 16 other CVEs. CVE-2026-129289, also critical, lets an unauthenticated attacker run PHP code through PHP-FPM where FastCGI connections are reused. Upgrade to PHP 8.5.13, 8.4.28, 8.3.37 or 8.2.36 now; PHP 8.1 and older get no fix.

Published 19 November 2026

Updating live, last update 18:40 GMT

Precursor Security

## What you should do now

1.  **Upgrade every PHP install** to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, including PHP inside container images, control panels and appliances. Restart PHP-FPM and rebuild containers. PHP 8.1 and older get no fix: move to a supported branch.
2.  **Check FastCGI connection reuse.** If nginx uses `fastcgi_keep_conn on` or Apache uses `enablereuse=on` towards PHP-FPM, those servers go first. Turn keep-alive off until patched.
3.  **Disable session upload progress** if you do not use it: `session.upload_progress.enabled = 0`. It was on by default before this release; the fix turns it off by default, but an explicit setting in `php.ini` or an FPM pool overrides that. It is the path to phpAfterShell and CVE-2026-115560.
4.  **On PHP 8.5,** confirm `zend.exception_ignore_args = 1` (as in `php.ini-production`) to block the demonstrated CVE-2026-129474 attack.
5.  **Patched PHP2Shell in October?** Patch again. Today's release completes the October fix for CVE-2026-109619.
6.  **On a distribution package?** Check your vendor's advisory for the CVE numbers rather than `php -v`; backports often keep the old version number.

## phpAfterShell live timeline

[14:43 GMT](#update-2026-11-19-1443)19 Nov 2026Pinned

### What we know so far

**What happened:** PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026, fixing 17 CVEs. Seven are critical (CVSS 9.2). The best known is **phpAfterShell** (CVE-2026-126714), named by its finder depthfirst: PHP's default file session handler can be made to deserialise attacker data.

**Also critical:** CVE-2026-129289, PHP-FPM request smuggling, which can run attacker PHP code without authentication where the front end reuses FastCGI connections. Depthfirst says phpAfterShell works with PHP's pre-fix defaults (file sessions and upload progress) and bypasses October's PHP2Shell fix. The fix turns upload progress off by default unless it is explicitly enabled. Other criticals need specific setups: mixed session serializers, a file error log with startup warnings, or PHP 8.5 with exception arguments enabled.

**What to do:** upgrade every PHP install to the fixed release for its branch and restart PHP-FPM. If you patched PHP2Shell in October, you still need this release. No exploitation in the wild has been reported so far, and EPSS and CISA's KEV catalogue have nothing yet.

**Quick version:** our [breakdown thread on X](https://x.com/PrecursorUK/status/2123420120055697616) covers the CVEs, who is exposed and what to do in nine posts.

[18:40 GMT](#update-2026-11-19-1840)19 Nov 2026

### Canada's Cyber Centre issues an advisory; Ondrej Sury PPA build pulled

**Canada:** the Canadian Centre for Cyber Security published [advisory AV26-1183](https://www.cyber.gc.ca/en/alerts-advisories/php-group-security-advisory-av26-1183), listing PHP before 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0 as affected and encouraging users and administrators to apply the updates.

**Correction on packages:** at 16:49 we reported that Ondrej Sury's PHP PPA had fixed builds for Ubuntu 26.04. Launchpad's [package listing](https://launchpad.net/~ondrej/+archive/ubuntu/php) now shows that 8.4.28 build as deleted, and its Ubuntu 22.04 and 24.04 packages remain on the October versions (8.4.27). There are no fixed packages in the PPA for any Ubuntu release at the time of writing. The official Docker images and php.net source releases are fixed.

[18:30 GMT](#update-2026-11-19-1830)19 Nov 2026

### Cygames takes Uma Musume and Granblue Fantasy offline to address the PHP vulnerability

Japanese games company Cygames ran emergency maintenance on two of its biggest titles "to address a PHP vulnerability", according to their official accounts.

**Granblue Fantasy:** the [game's account](https://x.com/granbluefantasy/status/2123346438826651989) announced maintenance from 22:00 Japan time (13:00 GMT) to address a PHP vulnerability, with no end time given. It [reported completion](https://x.com/granbluefantasy/status/2123472781124022651) at 02:45 Japan time (17:45 GMT).

**Uma Musume Pretty Derby:** the [official notice](https://umamusume.jp/news/detail?id=3555), titled "Maintenance for PHP vulnerability response", took the game offline from around 23:00 Japan time (14:00 GMT). The [account said](https://x.com/uma_musu/status/2123465612743889196) maintenance ended at 01:52 Japan time (16:52 GMT). Its user support page was also taken down for security maintenance.

Neither notice says whether the games were affected by any specific CVE or whether any harm occurred. Japan's GameBusiness.jp reports other Cygames titles were also part of the maintenance.

[18:07 GMT](#update-2026-11-19-1807)19 Nov 2026

### Cloudflare Radar publishes a phpAfterShell briefing with a step-by-step checklist

Cloudflare Radar's new Zero Wire service has published a [briefing on phpAfterShell and the six other critical PHP flaws](https://radar.cloudflare.com/zero-wire/php-november-2026-security-release-phpaftershell). It counts 17 advisories (7 critical, 4 high, 6 medium) and repeats PHP's note that the critical issues need non-default or uncommon setups.

Its recommended steps: find every PHP runtime serving web requests, including container images and managed hosting, and record the version, server API (FPM, mod\_php, CGI or LSAPI), session handler, upload progress setting and whether the front end reuses FastCGI connections. For distribution packages, check the full package version against the distribution's advisory. Then upgrade, rebuild images, restart the PHP-FPM master or Apache so every worker loads the new binary, and verify the version serving requests.

After upgrading, Cloudflare says to check whether any php.ini, FPM pool or virtual host still sets `session.upload_progress.enabled=1`, "because an explicit setting overrides the new default." Until upgrading, it lists PHP's interim mitigations per CVE and notes "these steps reduce exposure; they do not fix the flaws."

[17:57 GMT](#update-2026-11-19-1757)19 Nov 2026

### Puzzle & Dragons takes servers down for emergency security maintenance

GungHo Online Entertainment began [emergency maintenance](https://pad.gungho.jp/jp/notice/109) on its mobile game Puzzle & Dragons at 23:00 Japan time (14:00 GMT), the same window as the PHP release, with no end time set. Its notice, posted earlier on 19 November, gives the reason as "security enhancement" and says "no damage has been confirmed at this time". The notice does not mention PHP.

Japanese gaming site [Dengeki Online](https://news.google.com/search?q=%E3%83%91%E3%82%BA%E3%83%89%E3%83%A9%20PHP%20%E9%9B%BB%E6%92%83%E3%82%AA%E3%83%B3%E3%83%A9%E3%82%A4%E3%83%B3) reported the maintenance under the headline "PHP vulnerability again", linking it to the PHP security release. GungHo has not confirmed that link.

[17:09 GMT](#update-2026-11-19-1709)19 Nov 2026

### The Hacker News confirms upload progress is now off by default, and flags what that means

In an [explainer on phpAfterShell](https://thehackernews.com/2026/11/phpaftershell-explained-how-hackers.html), The Hacker News says it compared PHP's source code for the 21 October and 19 November releases. The built-in default for session upload progress "is on in 8.2.35, 8.3.36, 8.4.27 and 8.5.12, and off in 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0."

According to the article, the release notes do not mention the change, and the sample php.ini files still show the old setting in a commented-out line. It says "a php.ini file, distribution package, or hosting panel that switches the setting on will keep it on", and that apps which rely on upload progress will need it switched back on after the update where nothing else sets it.

The Hacker News also relays depthfirst's point that Linux distribution packages may include the fix without changing the PHP version number, "so the version number alone may not indicate whether a server is fixed". Neither PHP nor depthfirst reports any attacks using phpAfterShell. Korea's Yonhap News TV has also covered the release.

[16:49 GMT](#update-2026-11-19-1649)19 Nov 2026

### Belgium and Japan issue warnings; Ondrej Sury's PHP packages start shipping fixes

**Belgium:** the Centre for Cybersecurity Belgium published ["Warning: Multiple critical vulnerabilities affect PHP, Patch Immediately!"](https://ccb.belgium.be/advisories/warning-multiple-critical-vulnerabilities-affect-php-patch-immediately), saying the PHP-FPM and PHP-CGI flaws are "particularly concerning for internet-facing web infrastructure". It counts 18 CVEs with 8 critical; the PHP advisories rate 7 critical.

**Japan:** the National Cybersecurity Office [told operators](https://x.com/cyber_forecast/status/2123437173550800967) that PHP security patches were released after 23:00 Japan time and that administrators should check whether their systems are affected. Earlier in the day it had noted that, unlike PHP2Shell, the issues reportedly affect only certain environments.

**Packages:** Ondrej Sury's widely used [PHP PPA for Ubuntu](https://launchpad.net/~ondrej/+archive/ubuntu/php) now has 8.2.36, 8.3.37, 8.4.28 and 8.5.13 builds for Ubuntu 26.04. At 16:47 GMT its Ubuntu 22.04 and 24.04 builds were still on the October versions. _Correction, 18:40 GMT: Launchpad now lists the 26.04 build as deleted; see 18:40._ The official Ubuntu, Debian, Red Hat, SUSE and Amazon Linux packages are not fixed yet.

[16:35 GMT](#update-2026-11-19-1635)19 Nov 2026

### BleepingComputer covers the release; distributions still triaging

[BleepingComputer](https://www.bleepingcomputer.com/news/security/php-security-updates-fix-18-flaws-including-critical-rce-bugs/) reports "security updates for 18 vulnerabilities", citing Aikido's count, and leads with the PHP-FPM request smuggling flaw. It notes that "standard nginx and Apache configurations that do not reuse backend connections are not affected by the attack", that administrators who cannot update yet can disable persistent backend connections to PHP-FPM, and that CVE-2026-115560 was already disclosed in an informational advisory on 23 October.

Linux distributions have not shipped fixed PHP packages yet. Ubuntu's CVE tracker lists CVE-2026-126714 as needing triage, Debian's tracker shows unstable (sid) as vulnerable, SUSE lists PHP as affected or under analysis, and Amazon Linux shows fixes pending (see 15:18). The official Docker images are already updated.

[16:30 GMT](#update-2026-11-19-1630)19 Nov 2026

### CSIRT Italia: proof of concept available for CVE-2026-115560

Italy's national CSIRT, part of the National Cybersecurity Agency (ACN), has issued alert [AL14/261119/CSIRT-ITA](https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-php), rated high risk. It says CVE-2026-115560, the session serializer mismatch, "was already covered in alert AL07/261021/CSIRT-ITA" on 21 October and that a proof of concept for it is available online. Its CVE table lists a PoC as present for CVE-2026-115560 and no reported exploitation for any of the critical or high CVEs.

CSIRT Italia describes the condition as `session.serialize_handler` being set to `php_binary` or `php_serialize` and then changed to `php` at runtime before the session starts, with session upload progress enabled. It recommends updating to 8.2.36, 8.3.37, 8.4.28 or 8.5.13.

SecurityWeek has also covered the release under the headline "[PHP Patches Seven Critical RCE Vulnerabilities](https://www.securityweek.com/php-patches-seven-critical-rce-vulnerabilities/)".

[16:07 GMT](#update-2026-11-19-1607)19 Nov 2026

### Media round-up: Infosecurity Magazine links PHP2Shell attacks to Palo Alto firewalls too

[Infosecurity Magazine](https://www.infosecurity-magazine.com/news/php-releases-patches-fix-18/) reports "18 vulnerabilities, seven of which are marked critical" (its count appears to include the bundled uriparser CVE; the PHP advisories list 17). It says CVE-2026-115560 was disclosed by PHP on 23 October, two days after the PHP2Shell emergency fixes, and that exploitation of that bug "requires a highly specific and unlikely combination of conditions".

On PHP2Shell, the magazine notes Check Point's report of attacks on its gateways since 30 October and adds that "the exploitation activity also extended to Palo Alto Networks firewalls, with attackers targeting devices whose administrative interfaces were exposed to the internet."

Also covering the release: Poland's Sekurak ("request smuggling, UAF and the aftermath of php2shell"), Argentina's Infobae, and Korea's Yonhap and Cheonji Ilbo.

[15:48 GMT](#update-2026-11-19-1548)19 Nov 2026

### Yonhap covers the release; are today's releases still vulnerable? The advisories say no

South Korea's national news agency [Yonhap](https://www.yna.co.kr/view/AKR20261119185500017) reports 17 vulnerabilities in the release: 7 critical, 4 high and 6 moderate. It notes that the PHP team says some critical issues arise only in non-default environments, and cites W3Techs figures that PHP is used by about 68.1% of websites whose programming language can be identified.

Some posts on X claim the releases shipped today are still exposed to phpAfterShell. That appears to come from the version table in depthfirst's write-up, which describes the PHP source trees as of 17 November, before the final releases. The PHP advisory for [CVE-2026-126714](https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp) lists 8.2.36, 8.3.37, 8.4.28 and 8.5.13 as the patched versions.

A correction on our side: this page earlier said 18 CVEs. The PHP advisories cover 17 CVEs; the ChangeLog adds an 18th CVE number for the bundled uriparser library in 8.5.13 and 8.6.0, which has no PHP advisory.

[15:43 GMT](#update-2026-11-19-1543)19 Nov 2026

### The fix turns session upload progress off by default, unless you have set it on

The PHP advisory for [CVE-2026-115560](https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx) says "the fix disables session upload progress by default and rejects runtime changes to session settings, including `session.serialize_handler`, while upload progress is enabled." It warns that "an explicit setting overrides the new default", so a `php.ini`, FPM pool or virtual host that sets `session.upload_progress.enabled = On` keeps the feature, and the attack path, after upgrading.

CVE-2026-115560 was found by Dvir Sasson of ZEST Security, whose [write-up](https://www.zestsecurity.io/resources/content/php2shell-the-third-one-cve-2026-115560) calls it "PHP2Shell, the third one". ZEST says it reported the bug on 21 October, the day PHP2Shell was patched, after about five hours of research with a locally run open-weight model, and that it is not publishing exploit code. Its advice matches the advisory: upgrade, then search every `php.ini`, FPM pool and vhost for an explicit `session.upload_progress.enabled = On`.

Separately, the official Docker `php:8.6.0` image appeared at 15:32 GMT and `php:latest` now points to it (15:34 GMT).

[15:31 GMT](#update-2026-11-19-1531)19 Nov 2026

### Docker php:8.5.13 out: all four fixed branches now on Docker Hub

The official [php](https://hub.docker.com/_/php) image published `php:8.5.13` at 15:27 GMT, so fixed tags now exist for all four security releases: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. At 15:30 GMT there was no `php:8.6.0` tag yet and `php:latest` still pointed to the 5 November build, so images pinned to `latest` or a floating tag need checking after they update.

[15:29 GMT](#update-2026-11-19-1529)19 Nov 2026

### Docker php:8.4.28 out; 8.5.13 and 8.6.0 still pending

The official [php](https://hub.docker.com/_/php) image on Docker Hub published `php:8.4.28` at 15:22 GMT, joining 8.3.37 and 8.2.36. Tags for 8.5.13 and 8.6.0 were not yet available at 15:26 GMT, and `php:latest` still pointed to the 5 November build.

[15:28 GMT](#update-2026-11-19-1528)19 Nov 2026

### Context: PHP2Shell has already been exploited in the wild

phpAfterShell bypasses the fix for PHP2Shell, and PHP2Shell itself has been used in real attacks. [Check Point Research](https://research.checkpoint.com/2026/php2shell-exploitation-on-check-point-gateway/) reported on 12 November that, beginning on 30 October 2026, an attacker used PHP2Shell against unpatched Check Point Security Gateways (via Mobile Access portals) for initial access, then a local privilege escalation tracked as CVE-2026-123039.

According to Check Point, the attackers deployed PHP web shells and a backdoor it calls TSGA, pivoted to a VMware ESXi host and deployed a wiper against some Israeli organisations in a first wave, followed by a broader second wave on 2 November. [The Hacker News](https://thehackernews.com/2026/11/hackers-exploit-php2shell-flaws-in.html) covered the report on 13 November. No exploitation of today's CVEs has been reported.

[15:18 GMT](#update-2026-11-19-1518)19 Nov 2026

### Amazon Linux: PHP fixes pending, PHP 8.1 marked "No Fix Planned"; Docker 8.3.37 out

Amazon's CVE pages for [CVE-2026-126714](https://explore.alas.aws.amazon.com/CVE-2026-126714.html) and [CVE-2026-129289](https://explore.alas.aws.amazon.com/CVE-2026-129289.html) list the php8.2, php8.3, php8.4 and php8.5 packages on Amazon Linux 2023 as Pending Fix, and php8.1 as No Fix Planned. Amazon Linux 2's PHP 8.2 Extra is also pending; its core php package is listed as pending for phpAfterShell and not affected by the FPM smuggling bug. Amazon scores CVE-2026-129289 at 9.8 on CVSS 3.1.

On Docker Hub, the official `php:8.3.37` image appeared at 15:15 GMT, after `php:8.2.36` at 15:07. Tags for 8.4.28, 8.5.13 and 8.6.0 were still pending at 15:16 GMT.

[15:13 GMT](#update-2026-11-19-1513)19 Nov 2026

### Also in the release: bundled uriparser fix, and the first fixed Docker image

The [PHP 8 ChangeLog](https://www.php.net/ChangeLog-8.php) lists one more CVE that is not among the 17 GitHub advisories: PHP 8.5.13 and 8.6.0 upgrade the bundled uriparser library, used by the URI extension added in PHP 8.5, to version 1.0.3 for CVE-2026-48841.

Docker Hub's official [php image](https://hub.docker.com/_/php) has started publishing fixed builds: the `php:8.2.36` tag appeared at 15:07 GMT. Tags for 8.3.37, 8.4.28, 8.5.13 and 8.6.0 were not yet available at 15:11 GMT, and `php:latest` was still the 5 November build.

[15:12 GMT](#update-2026-11-19-1512)19 Nov 2026

### The Hacker News: "PHP Fixes 7 Critical Flaws"

The Hacker News has covered the release under the headline "PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution", describing fixes for PHP 8.2 to 8.6 ([article](https://thehackernews.com/2026/11/php-fixes-7-critical-flaws-including.html)). On phpAfterShell it says the flaw "affects its default file-based session storage" and that interrupted writes "can enable unsafe deserialization and potential RCE if a suitable gadget chain exists".

[15:00 GMT](#update-2026-11-19-1500)19 Nov 2026

### heise: critical PHP flaws need preconditions, not standard installations

German tech outlet [heise online](https://www.heise.de/news/PHP-behebt-17-Sicherheitsluecken-vier-erlauben-Ausfuehrung-von-Schadcode-11531249.html) reports 17 fixes, four of them critical code execution flaws (CVE-2026-129289, CVE-2026-115560, CVE-2026-129496 and CVE-2026-129474), and says the critical holes can only be exploited with preconditions, not on standard installations. It notes the FPM smuggling bug needs `FCGI_KEEP_CONN` set, which is off by default.

For comparison, the PHP advisories rate seven issues critical, and depthfirst says phpAfterShell (CVE-2026-126714), which is not among heise's four, works with file sessions and upload progress, both PHP defaults.

[14:59 GMT](#update-2026-11-19-1459)19 Nov 2026

### Cloudflare WAF rules for three PHP CVEs, in log mode on paid plans

Cloudflare CTO Dane Knecht [says](https://x.com/dok2001/status/2123429793425465389) Cloudflare has WAF rules for CVE-2026-129289 (PHP-FPM request smuggling), CVE-2026-15353 and CVE-2026-129506 (the two SOAP bugs). They are in log mode on paid plans, with "more rules to come". His advice: "Check what they match on your traffic, then switch to block. Upgrade Ruby and PHP either way."

The rules listed do not include phpAfterShell (CVE-2026-126714).

[14:56 GMT](#update-2026-11-19-1456)19 Nov 2026

### What the attack looks like, according to depthfirst

Depthfirst's write-up says its method takes repeated tries: the controller reached the target within 10 to 11 attempts in fresh runs, each using a new session ID and three requests. The behaviour it describes:

`multipart/form-data` POSTs carrying a `PHP_SESSION_UPLOAD_PROGRESS` field, a carrier and a replacement upload against the same session ID, then a GET with that session cookie; PHP workers killed by the out-of-memory killer or by hard timeouts during uploads; and, for one variant, multipart field names with deep bracket notation used to slow parsing.

[14:55 GMT](#update-2026-11-19-1455)19 Nov 2026

### How exposed is phpAfterShell? What PHP, depthfirst and the PHP manual say

PHP's pre-announcement said the critical issues "require either non-default configuration or uncommon setups". Depthfirst says phpAfterShell needs file-based sessions, PHP's default handler, and session upload progress, which the [PHP manual](https://www.php.net/manual/en/session.configuration.php) lists as on by default (`session.upload_progress.enabled` = 1) in releases before today's fix. According to depthfirst, the application does not need an upload controller or a `session_start()` call on the targeted URL.

The PHP advisory says code execution requires "an application with a suitable deserialization gadget chain". Depthfirst says its full chain uses a memory-corruption bug in PHP's own native classes and "does not depend on an application-defined gadget class"; it has withheld those details for coordinated disclosure.

Depthfirst's write-up also describes the limits: the attack has to stop a PHP worker at a precise point in the file write, which it did with memory pressure or timeouts on Apache, using a controller that adapts to each server. It adds that even without objects, a spliced session can replace "identity, authorization, CSRF, password-reset, cart, or workflow state". Its interim mitigation is `session.upload_progress.enabled = 0`.

[14:54 GMT](#update-2026-11-19-1454)19 Nov 2026

### Depthfirst write-up: phpAfterShell bypasses the PHP2Shell fix

Depthfirst researcher Yuhang Wu has published the [technical write-up](https://depthfirst.com/research/phpaftershell). It started as a review of October's PHP2Shell patch, which stopped objects being created while PHP handles upload progress. The patch did not make the session file update itself safe.

When upload progress is on, PHP opens the session file and rewrites it while it is still parsing an unauthenticated multipart request, before the target script runs. That rewrite was not atomic. If the worker dies part way through, the file is left with the start of the new session joined to the end of the old one, and carefully chosen string lengths make PHP read leftover bytes as new session entries and serialised objects. The next ordinary `session_start()` then loads them. In the write-up's words, "the application contributes only its normal use of Sessions".

Depthfirst found two variants: one where the worker is killed during the write (it used memory pressure to trigger the out-of-memory killer), and one where it dies between the write and the truncate that follows. The fix truncates the file to zero before writing. Affected: every release before 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The official end-of-life mitigation branches for 7.4, 8.0 and 8.1 are not affected, but older unpatched builds of those versions are.

[14:42 GMT](#update-2026-11-19-1442)19 Nov 2026

### Germany's BSI rates the PHP release high

CERT-Bund, part of Germany's BSI, published advisory [WID-SEC-2026-4684](https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4684), "PHP: multiple vulnerabilities", rated high, at 12:32 GMT, ahead of the release itself. It is the first national agency notice we have seen for this release. The UK NCSC's most recent PHP alert is still the one from October for PHP2Shell.

[14:41 GMT](#update-2026-11-19-1441)19 Nov 2026

### Also high: FPM worker to root, HTTPS sent in plaintext, Phar signature bypass

**CVE-2026-129291 (8.8)**: [a PHP-FPM use-after-free](https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m) lets someone who can already run PHP code in a worker execute commands as the FPM master, which commonly runs as root. It needs `catch_workers_output` enabled, which the official PHP-FPM Docker images do. In a container it gives the master's container privileges, not a container escape.

**CVE-2026-128064 (8.2)**: [PHP's HTTP and FTP stream wrappers](https://github.com/php/php-src/security/advisories/GHSA-f6gg-rchx-xw8j) send data unencrypted when the scheme has a capital S, such as `HTTPS://` or `httpS://`, including after a redirect. Applications using `file_get_contents()` or `fopen()` could leak credentials or tokens to anyone on the network path. Interim fix: lowercase schemes and validate redirect targets.

**CVE-2026-127960 (8.7)**: a malicious HTTP server can tie up PHP's CPU with folded response headers. **CVE-2026-128090 (7.7)**: an attacker who can modify an OpenSSL-signed Phar can downgrade its signature to a plain hash and have PHP accept it.

[14:40 GMT](#update-2026-11-19-1440)19 Nov 2026

### Patched PHP2Shell in October? You are not covered

Two of the critical fixes finish the job started by October's PHP2Shell patch for CVE-2026-109619. [CVE-2026-129481](https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7) is described by the PHP team as "an incomplete fix for CVE-2026-109619" (session shutdown use-after-free, PHP 8.3 and later), and [CVE-2026-129182](https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m) covers further ways the same fatal-error backtrace can be reused after shutdown (PHP 8.5).

Also 8.5 only: [CVE-2026-129474](https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2), a use-after-free in magic method backtraces with confirmed remote code execution. The demonstrated attack needs `zend.exception_ignore_args=0`; the standard `php.ini-production` sets it to 1, which blocks that path.

The October releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) contain none of today's fixes.

[14:39 GMT](#update-2026-11-19-1439)19 Nov 2026

### Timezone cache use-after-free can crash FPM workers (CVE-2026-129496)

[CVE-2026-129496](https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv) (critical, all branches) is triggered when PHP writes a warning to a file-based `error_log` during startup, for example from an invalid `date.timezone`, on a non-thread-safe build. A later warning early in a request, such as exceeding `max_input_vars`, then touches freed memory. The PHP team says a crafted HTTP request has crashed an FPM worker with default limits; code execution was shown locally with extra configuration.

[14:38 GMT](#update-2026-11-19-1438)19 Nov 2026

### Two session bugs reach RCE through deserialisation

**phpAfterShell, CVE-2026-126714**: found by depthfirst, which named it. PHP's default `files` session handler did not clear a session file before rewriting it, so an interrupted write can leave a mix of old and new data that later deserialises into attacker-chosen objects. The advisory says code execution needs a gadget chain in the application; depthfirst's own chain uses PHP's native classes instead (see 14:55). Depthfirst says it reported the bug in late October and that "any application running an affected PHP version with file-based sessions is exposed until PHP is upgraded" ([depthfirst](https://depthfirst.com/phpaftershell), [advisory](https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp)).

**CVE-2026-115560**: [session upload progress](https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx) can write data in one session format that is later read in another, turning part of a key into serialised objects. It needs upload progress enabled and mixed serializers (for example `php_serialize` written, `php` read) on a shared session store; the reporters demonstrated command execution with Guzzle and Monolog gadgets.

Interim mitigation for both, from depthfirst and the advisories: set `session.upload_progress.enabled = 0` if you do not need it, and avoid storing large user-controlled strings in sessions. Sessions in Redis or a database are not affected by the phpAfterShell file-write bug.

[14:37 GMT](#update-2026-11-19-1437)19 Nov 2026

### PHP-FPM request smuggling can run attacker PHP code (CVE-2026-129289)

[CVE-2026-129289](https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6) (critical, all branches) is rated critical for all branches. PHP failed to discard unread request-body bytes before reusing a persistent PHP-FPM connection. An unauthenticated attacker can hide a forged FastCGI request in the body and, according to the PHP team, "bypass front-end routing and execute attacker-controlled PHP code with the privileges of the worker". The forged request can also change administrator-level PHP settings for later requests.

Exposure depends on the front end keeping backend connections open: nginx `fastcgi_keep_conn on`, Apache `mod_proxy_fcgi` with `enablereuse=on`, HAProxy FastCGI with kept connections, or LSAPI. It also needs an application path that opens `php://input` without reading it to the end, which frameworks can do before routing. The advisory says standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated attack.

[14:08 GMT](#update-2026-11-19-1408)19 Nov 2026

### PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 released: 17 CVEs, 7 critical

The PHP team published the releases on [php.net](https://www.php.net/) just after 14:00 GMT, each described as "a security release", and posted 17 GitHub security advisories between 14:05 and 14:09 GMT. PHP 8.5.13 fixes 17 CVEs, 8.4.28 fixes 14, and 8.3.37 and 8.2.36 fix 13 each ([ChangeLog](https://www.php.net/ChangeLog-8.php)).

Seven are rated critical (CVSS 4.0 9.2): CVE-2026-129289, CVE-2026-126714, CVE-2026-115560, CVE-2026-129496, CVE-2026-129474, CVE-2026-129481 and CVE-2026-129182. PHP 8.1 and older are end of life and get no fixes.

PHP 8.6.0, the new major version, was released the same afternoon and includes the same 17 security fixes as 8.5.13 according to the ChangeLog, so upgrading to 8.6.0 also patches. For most teams the point release on your current branch is the faster, lower-risk fix.

[Announced](#update-2026-11-18-announced)18 Nov 2026

### PHP pre-announces a critical security release

The PHP security team announced releases for 19 November between 14:00 and 14:30 UTC, fixing vulnerabilities in all supported versions with "the highest severity" rated critical. It added that "the issues rated CRITICAL require either non-default configuration or uncommon setups", a caveat that holds for most, though not all, of what shipped ([php.net](https://www.php.net/)).

[October](#update-2026-10-21-october)21 Oct 2026

### Four weeks earlier: PHP2Shell

On 21 October PHP shipped emergency fixes for PHP2Shell (CVE-2026-109618 and CVE-2026-109619), two critical remote code execution bugs. Today's release includes follow-up fixes for CVE-2026-109619 and new, unrelated critical flaws. Our [PHP2Shell live blog](/blog/php2shell-critical-php-rce-vulnerabilities) covers the October release.

## phpAfterShell and PHP release key facts

Fixed in

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, released 19 November 2026. PHP 8.6.0, released the same day, includes the same fixes. PHP 8.1 and older get no fix.

Scale

17 CVEs with PHP advisories: 7 critical (CVSS 4.0 9.2), 4 high and 6 medium. 8.5.13 and 8.6.0 also update bundled uriparser (CVE-2026-48841).

phpAfterShell

CVE-2026-126714 in the default files session handler, reachable via upload progress (on by default before the fix). Found by depthfirst; bypasses the PHP2Shell fix.

FPM smuggling

CVE-2026-129289: PHP-FPM request smuggling runs attacker PHP code, unauthenticated, where the front end reuses FastCGI connections (nginx fastcgi\_keep\_conn, Apache enablereuse).

Status

No exploitation in the wild reported. CSIRT Italia says a proof of concept for CVE-2026-115560 is available online. Not in CISA KEV; no EPSS scores yet.

Interim steps

FastCGI keep-alive off, session.upload\_progress.enabled = 0, zend.exception\_ignore\_args = 1 on PHP 8.5.

## Every CVE in the 19 November PHP release

CVE

Severity

Flaw

Branches

Exposed when

CVE-2026-129289

Critical 9.2

PHP-FPM request smuggling, attacker PHP code execution

All

FastCGI connection reuse (keep\_conn / enablereuse), LSAPI

CVE-2026-126714

Critical 9.2

phpAfterShell: interrupted session write leads to deserialisation

All

Default files sessions with upload progress (on by default before the fix); bypasses the PHP2Shell fix

CVE-2026-115560

Critical 9.2

Session serializer mismatch leads to deserialisation

All

Upload progress on, mixed serializers on a shared store

CVE-2026-129496

Critical 9.2

Timezone cache use-after-free

All

Startup warning to file error\_log, non-thread-safe build

CVE-2026-129481

Critical 9.2

Use-after-free after interrupted session shutdown

8.3, 8.4, 8.5

Incomplete fix for PHP2Shell CVE-2026-109619

CVE-2026-129474

Critical 9.2

Use-after-free in magic method backtraces

8.5

zend.exception\_ignore\_args=0

CVE-2026-129182

Critical 9.2

Use-after-free via fatal error backtrace after shutdown

8.5

Follow-up to PHP2Shell CVE-2026-109619

CVE-2026-129291

High 8.8

PHP-FPM epoll use-after-free, worker to master (often root)

All

Local code execution; catch\_workers\_output on

CVE-2026-127960

High 8.7

Denial of service via folded HTTP response headers

All

App fetches URLs from a malicious server

CVE-2026-128064

High 8.2

HTTPS/FTPS with a capital S sent unencrypted

All

Stream wrappers, including redirects

CVE-2026-128090

High 7.7

Phar OpenSSL signature bypass

All

Attacker can modify a signed Phar

CVE-2026-129538

Medium 6.9

PHP-CGI out-of-bounds read and write

All

php-cgi with inconsistent path info

CVE-2026-129501

Medium 6.3

Double free in DOM XML serialisation

8.4, 8.5

saveXml() on attacker XML or HTML

CVE-2026-15353

Medium 6.3

SOAP information disclosure

All

Exposed SOAP endpoint or client

CVE-2026-129506

Medium 6.3

SOAP use-after-free with DTD entities

All

Exposed SOAP endpoint

CVE-2026-129438

Medium 6.3

Incorrect RFC 3986 URI serialisation

8.5

Very large attacker URIs

CVE-2026-129292

Medium 5.3

PHP-FPM status page XSS

All

FPM full status page viewed by an operator

Severities and conditions from the [PHP security advisories](https://github.com/php/php-src/security/advisories); branch coverage from the [PHP 8 ChangeLog](https://www.php.net/ChangeLog-8.php). All are fixed in 8.5.13, 8.4.28, 8.3.37 and 8.2.36 where the branch is affected. CVE-2026-129438 is listed in the 8.5 ChangeLog only.

## Why this release matters: PHP-FPM is everywhere

PHP runs about 68% of websites whose server-side language can be identified, according to W3Techs figures cited by depthfirst, and PHP-FPM behind nginx or Apache is the standard way to run it. A flaw that lets an unauthenticated request become a forged FastCGI request goes to the heart of that stack.

This is also the second critical PHP release in four weeks, and several of today's fixes were found by AI-assisted research. The advisories include working proof-of-concept chains,.

## Sources and advisories

-   [php.net: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 released (19 November 2026)](https://www.php.net/)
-   [PHP 8 ChangeLog](https://www.php.net/ChangeLog-8.php)
-   [PHP security advisories (GitHub)](https://github.com/php/php-src/security/advisories)
-   [depthfirst: phpAfterShell (CVE-2026-126714)](https://depthfirst.com/phpaftershell)
-   [CVE-2026-129289: PHP-FPM request smuggling](https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6)
-   [CVE-2026-126714: partially overwritten session files](https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp)
-   [CVE-2026-115560: session serializer mismatch](https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx)
-   [CVE-2026-129496: timezone cache use-after-free](https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv)
-   [CERT-Bund (BSI) WID-SEC-2026-4684](https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4684)

## phpAfterShell and PHP release FAQs

### What is phpAfterShell?

phpAfterShell is the name depthfirst gave to CVE-2026-126714, a critical (CVSS 9.2) flaw in PHP's default file-based session handler. An interrupted session write can leave a mixed file that later deserialises into attacker-chosen objects, which can lead to remote code execution; depthfirst says its full chain uses PHP's own native classes rather than application code. It bypasses October's PHP2Shell fix and was fixed on 19 November 2026.

### Which PHP versions fix phpAfterShell and the other CVEs?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, released on 19 November 2026. Earlier releases in each branch are affected, including the October PHP2Shell releases (8.5.12, 8.4.27, 8.3.36, 8.2.35).

### How many vulnerabilities did PHP fix on 19 November 2026?

17 CVEs with PHP security advisories: 17 in PHP 8.5.13, 14 in 8.4.28 and 13 each in 8.3.37 and 8.2.36. Seven are rated critical with a CVSS 4.0 score of 9.2.

### What is CVE-2026-129289?

CVE-2026-129289 is a critical PHP-FPM request smuggling flaw. Unread request-body bytes can form a forged FastCGI request on a reused connection, letting an unauthenticated attacker execute PHP code. It needs a front end that keeps backend connections open, such as nginx fastcgi\_keep\_conn on or Apache enablereuse=on.

### Am I affected by the PHP-FPM request smuggling flaw?

You are in scope if you run PHP-FPM or LSAPI behind a front end that reuses backend connections (nginx fastcgi\_keep\_conn on, Apache mod\_proxy\_fcgi enablereuse=on, HAProxy FastCGI with kept connections) and an application path opens php://input without reading it fully. Configurations that close the FastCGI connection after each request are not affected by the demonstrated attack.

### We patched PHP2Shell in October. Are we protected?

No. The October releases do not contain these fixes, and two of the new critical CVEs (CVE-2026-129481 and CVE-2026-129182) complete the October fix for CVE-2026-109619. Upgrade again.

### Is phpAfterShell being exploited?

No exploitation in the wild had been reported as of 19 November 2026, and none of the CVEs were in CISA's Known Exploited Vulnerabilities catalogue. Several advisories include working proof-of-concept chains, so expect that to change.

### How do I mitigate phpAfterShell if I cannot upgrade yet?

Set session.upload\_progress.enabled = 0 in php.ini and restart PHP if you do not need upload progress, and limit untrusted data stored in sessions. This removes the easiest path but not the flaw, so upgrade as soon as possible.

### Are WordPress, Laravel and Drupal sites affected?

Yes, potentially. The flaws are in PHP itself, so any application on an affected PHP version can be in scope depending on its configuration. Frameworks with magic method facades and request handling that opens php://input early are named in the advisories as relevant.

### Does storing sessions in Redis protect against phpAfterShell?

Redis, database and other non-file session handlers are not affected by the phpAfterShell file-write defect. CVE-2026-115560 can still apply where session upload progress and mixed serializers share a store.

### What should I do about PHP 8.1 or older?

PHP 8.1 and older are end of life and receive no fixes. Move to a supported branch (8.2 or later) and apply the 19 November release.

### My distribution package still shows an old PHP version. Am I patched?

Distributions often backport fixes without changing the upstream version number, so php -v is not proof either way. Check your vendor's security advisory or changelog for the CVE numbers.

### Which PHP settings reduce my exposure today?

Turn off FastCGI keep-alive to PHP-FPM, set session.upload\_progress.enabled = 0 if unused, set zend.exception\_ignore\_args = 1 on PHP 8.5, disable catch\_workers\_output if you do not need it, fix any startup warnings in the PHP error log, and lowercase https and ftps URL schemes in code. None replace the upgrade.

## Related

-   [PHP2Shell live blog: the critical PHP RCE from October 2026](/blog/php2shell-critical-php-rce-vulnerabilities)
-   [NGINX2Root live blog: the critical nginx RCE disclosed this week](/blog/nginx2root-critical-nginx-rce-vulnerabilities)
-   [Vulnerability management: find and prioritise unpatched PHP](/services/defensive-security/vulnerability-management)
-   [EdgeProtect attack surface management: see what you expose to the internet](/services/defensive-security/edge-protect-attack-surface-management)
-   [Web application penetration testing: test your PHP applications](/services/offensive-security/web-application-penetration-test)
-   [Incident response: if you think you have been compromised](/services/defensive-security/incident-response)

## Need help responding to phpAfterShell?

Precursor's CREST-accredited SOC monitors for active exploitation 24/7. If you need help finding exposed PHP and PHP-FPM servers, prioritising patching or testing your applications, we can help.

[Contact Precursor](/contact) [Our SOC Service](/services/defensive-security/security-operations-centre)