# phpAfterShell: PHP2Shell fix bypassed, new PHP updates from 19 November 2026

> URL: https://maxanoo.com/phpaftershell-php-vulnerability-update-november-2026/ · Autor: Sebastian · Veröffentlicht: 2026-11-19 · Aktualisiert: 2026-11-19

The October PHP2Shell fix is not enough: phpAfterShell (CVE-2026-126714) and other critical vulnerabilities mean PHP needs updating again. Which versions are safe and what website and shop owners should do now.

Four weeks after [PHP2Shell](/php-alert-two-critical-vulnerabilities-patch-today/), the PHP project released its next security updates on 19 November 2026. Among them is **phpAfterShell** (CVE-2026-126714): a vulnerability that gets around the October PHP2Shell fix by a different route. On top of that come two bugs the October patch missed. In total the releases fix around 20 CVEs, most of them rated critical at 9.2 (CVSS 4.0).

## In short

If your website or online shop runs on PHP, for example WordPress, Magento, Shopware or another PHP CMS, this affects you. The October update is no longer enough. Have PHP updated to one of the versions below, or ask your hosting provider when they will do it. If nobody takes care of this for you, [I am happy to help](/contact/). No attacks on the new vulnerabilities are known so far. With PHP2Shell, however, they started within a few days.

## The updates

- PHP 8.5 → **8.5.13**
- PHP 8.4 → **8.4.28**
- PHP 8.3 → **8.3.37**
- PHP 8.2 → **8.2.36**
- PHP **8.6.0**, released the same day, already contains the fixes.

The October versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are therefore out of date. PHP 8.1 and older no longer receive updates from the PHP project, and PHP 8.2 reaches end of life on 31 December 2026.

Linux distributions often ship fixes without changing the version number. Whether a Debian, Ubuntu or Red Hat package is patched is shown in the package changelog, not in the version number. On the evening of 19 November, Debian and Ubuntu had no fixed packages yet; the official Docker images had already been updated.

## What is phpAfterShell?

By default, PHP stores sessions as files on the server. They hold, for example, who is logged in. During file uploads PHP can also write the upload progress into this session file (`session.upload_progress`, enabled by default). PHP overwrites the file in two steps: write, then truncate to the new length. If the PHP process is killed in between, for instance by running out of memory or hitting a time limit, a mix of the new beginning and the old remainder is left behind.

The security researchers at depthfirst show that an attacker can prepare this remainder so that PHP reads it as session values and objects on the next `session_start()`. That allows login state, roles or CSRF tokens to be swapped. Combined with another, not yet published memory bug in a PHP-native class, this becomes code execution on the server, without the application itself having to contain a weakness. The attack does not require a login.

The PHP2Shell fix only restricted which objects may be created while upload progress is processed. The non-atomic file overwrite remained. Affected are therefore installations with file-based sessions and upload progress enabled, which is the default. If you store sessions in Redis or a database, phpAfterShell does not affect you, though other vulnerabilities in this release may.

## What the PHP2Shell fix missed

- **CVE-2026-129481** (PHP 8.3 to 8.5): use-after-free while cleaning up an interrupted session. Can crash PHP workers and possibly lead to code execution.
- **CVE-2026-129182** (PHP 8.5 only): use-after-free via an error state that is filled again after a request has ended. Closely related to CVE-2026-109619 from October.

## More critical vulnerabilities in the same release

- **CVE-2026-115560**: mismatched session serializers can lead to code execution. According to CSIRT Italia, a public proof of concept exists. For this issue PHP had already recommended disabling upload progress in October.
- **CVE-2026-129496** (date extension): use-after-free that can be triggered remotely without a login.
- **CVE-2026-129289** (PHP-FPM): requests can get mixed up when the web server reuses FastCGI connections, for example nginx with `fastcgi_keep_conn on` or Apache with `enablereuse=on`.
- **CVE-2026-129474** (PHP 8.5): use-after-free that can lead to code execution.
- Plus bugs in SOAP, Phar, DOM, CGI and the URI extension, and a local privilege escalation in PHP-FPM (CVE-2026-129291).

## How dangerous is it?

That is disputed. In its advance notice PHP says the critical issues require a non-default configuration or uncommon setups. depthfirst disagrees: phpAfterShell works with default settings, they say. The attack is not trivial: it takes several attempts and has to be tuned to the target server. depthfirst is still holding back the full exploit chain.

No exploitation of the new vulnerabilities is known yet. PHP2Shell, by contrast, was attacked within days of the patch and has been in the US agency CISA's catalogue of actively exploited vulnerabilities since 26 October. I would not bet on it taking longer this time.

## Am I affected? How to check your PHP version

**Without technical access:** ask your hosting provider or agency which PHP version your website runs and whether the updates from 19 November have been applied. Many hosting panels such as Plesk, cPanel or ISPConfig show the PHP version in the website settings. In WordPress you will find it under *Tools → Site Health → Info*. If your hosting provider or agency gives no clear answer, [I am glad to take a look](/contact/).

**With server access:** check the version that actually serves web requests, not just `php -v` on the command line. CLI and PHP-FPM can differ. For distribution packages, the package changelog is what counts (look for CVE-2026-126714).

## What you should do now

1. **Apply the update** to 8.5.13, 8.4.28, 8.3.37, 8.2.36 or 8.6.0, via your package source (distribution, Ondřej PPA, Remi, Docker image) or your hosting provider. Then restart PHP-FPM or Apache.
2. **Until then, disable upload progress:** `session.upload_progress.enabled=0` in `php.ini`, the FPM pool or the server configuration, not via `ini_set()` or `.user.ini`, and restart all workers. Hardly any application needs this feature. After updating, also check that it is not explicitly switched on somewhere.
3. **Do not reuse FastCGI connections** until patched: turn off `fastcgi_keep_conn` in nginx or `enablereuse` in Apache.
4. **PHP 8.1 and older:** plan the upgrade now. For Magento 2 the supported PHP version depends on the Magento version, so this needs lead time.
5. **Keep an eye on the logs:** watch for bursts of uploads (`multipart/form-data`) with a `PHP_SESSION_UPLOAD_PROGRESS` field, PHP processes killed by memory or time limits during uploads, and new PHP files in upload directories.

Would you rather not apply the update yourself, or does your server run several PHP versions and pools? [Write to me](/contact/) and I will take care of it.

Sources: [depthfirst: phpAfterShell](https://depthfirst.com/research/phpaftershell) · [php.net: PHP 8 changelog](https://www.php.net/ChangeLog-8.php) · [php.net: 2026 announcements](https://www.php.net/archive/2026.php) · [The Hacker News](https://thehackernews.com/2026/11/php-fixes-7-critical-flaws-including.html) · [Precursor Security: live updates](https://www.precursorsecurity.com/blog/phpaftershell-critical-php-rce-vulnerabilities). As of the evening of 19 Nov 2026.
