---
title: "Beyond phpAfterShell: Triaging CVE-2026-126714 and PHP&#8217;s November 2026 Critical RCEs"
url: "https://www.armorcode.com/blog/phpaftershell-cve-2026-126714-php-critical-rces"
markdown_url: "https://www.armorcode.com/blog/phpaftershell-cve-2026-126714-php-critical-rces.md"
llm_canonical: "https://www.armorcode.com/blog/phpaftershell-cve-2026-126714-php-critical-rces.md"
canonical_for_llm: true
entity_type: "Article"
primary_entity: "Beyond phpAfterShell: Triaging CVE-2026-126714 and PHP&#8217;s November 2026 Critical RCEs"
citation_value: "Published on ArmorCode; canonical URL https://www.armorcode.com/blog/phpaftershell-cve-2026-126714-php-critical-rces."
last_updated: "2026-11-20T10:58:27-08:00"
---

<h1>Beyond phpAfterShell: Triaging CVE-2026-126714 and PHP&amp;#8217;s November 2026 Critical RCEs</h1>

<h2>What is phpAfterShell (CVE-2026-126714)? One PHP release, seven Critical CVEs</h2>

On November 19, 2026, PHP shipped **8.5.13, 8.4.28, 8.3.37 and 8.2.36**, alongside the general release of **PHP 8.6.0**. Together they fix 17 vulnerabilities (18 CVE IDs, counting a bundled uriparser update), and **seven are rated Critical at CVSS v4.0 9.2**. Several of the Critical ones can lead to remote code execution (RCE). None has been reported exploited in the wild, and none is in CISA’s Known Exploited Vulnerabilities catalog.

> **Naming note:** phpAfterShell is the name for one vulnerability, **CVE-2026-126714**, which [depthfirst](https://depthfirst.com/phpaftershell) found in PHP’s file-based session handling. It does not cover the whole release. The other Critical CVEs, such as the session serializer bug (CVE-2026-115560) and the PHP-FPM request smuggling bug (CVE-2026-129289), are separate flaws with different preconditions. This release is also separate from October’s [PHP2Shell](https://www.armorcode.com/blog/php2shell-rce) (CVE-2026-109618 and CVE-2026-109619): the October releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) do not contain these fixes.

<h2>Which PHP versions are affected?</h2>

| **Branch** | **Affected** | **Fixed** | **Critical CVEs that apply** |
| --- | --- | --- | --- |
| PHP 8.5 | Before 8.5.13 | 8.5.13 | All 7 |
| PHP 8.4 | Before 8.4.28 | 8.4.28 | 5 (all except CVE-2026-129182 and CVE-2026-129474) |
| PHP 8.3 | Before 8.3.37 | 8.3.37 | 5 (same as 8.4) |
| PHP 8.2 | Before 8.2.36 | 8.2.36 (end of life December 31, 2026) | 4 (also excludes CVE-2026-129481) |
| PHP 8.6 | Pre-release builds before 8.6.0 | 8.6.0 | Fixes included in 8.6.0 |
| PHP 8.1 and earlier | End of life | No upstream release | PHP says older releases may also be affected by CVE-2026-115560, and the FPM bug dates to 5.6.0 |

<h2>The seven Critical CVEs and their preconditions</h2>

Each Critical CVE has its own conditions, so a server can be exposed to one and not another. The phpAfterShell row is highlighted.

| **CVE** | **Issue** | **Preconditions** |
| --- | --- | --- |
| CVE-2026-126714 (phpAfterShell) | Session files: a non-atomic write leaves a malformed file that is read back as objects | The default file session handler (session.save_handler=files). A session write is interrupted, for example by a memory limit or timeout. The attacker can shape the session data, most easily through upload progress or large user-controlled strings in the session. Code execution also needs a usable gadget chain in application or library code. Redis, database and other non-file handlers are not affected. PHP 8.2 to 8.5. |
| CVE-2026-115560 | Session serializer mismatch, disclosed October 23, leads to object injection | Upload progress enabled (the default before this release), and the session store is read with a different serializer than it was written with. That happens when code switches the handler with ini_set() before session_start(), or when separate apps, FPM pools, vhosts or CLI jobs share one store with different serializers. Command execution is documented with Guzzle and Monolog gadget chains. PHP 8.2 to 8.5. |
| CVE-2026-129289 | PHP-FPM request smuggling: leftover request-body bytes become a second FastCGI request | The front end reuses FastCGI connections (nginx fastcgi_keep_conn on, Apache enablereuse=on). The application opens php://input without reading it fully, which frameworks can do before routing or authentication. The attacker knows the path of one existing PHP script. No memory corruption or gadget chain is needed. Default setups that close the connection per request are not affected. PHP 8.2 to 8.5; on LiteSpeed LSAPI, PHP reports disruption and not code execution. |
| CVE-2026-129496 | Date extension timezone cache use-after-free | A non-thread-safe build that logs a startup diagnostic to a file-based error_log, followed by an early-request diagnostic in a fresh or recycled worker. A crafted request can crash FPM, mod_php or CGI workers. Code execution has been shown locally with known memory addresses. PHP 8.2 to 8.5. |
| CVE-2026-129481 | Use-after-free after an interrupted session shutdown | A fatal error in a callback during session shutdown (such as a user-defined stream wrapper’s stream_close()) leaves a stale pointer that a later request on the same worker frees. PHP calls it an incomplete fix for October’s CVE-2026-109619. Upload progress is not needed. PHP 8.3 to 8.5 (not 8.2). Code execution has not been demonstrated. |
| CVE-2026-129182 | Engine use-after-free: a stale fatal-error backtrace is reused after shutdown | PHP 8.5 only. Needs per-path or per-directory settings (such as max_memory_limit, or zlib.output_compression with output_handler, including via .user.ini or PHP_VALUE/PHP_ADMIN_VALUE) that trigger a fatal error during shutdown INI restoration, plus an early diagnostic in a subsequent request. Covers further exploitation scenarios for CVE-2026-109619. Code execution has not been demonstrated. |
| CVE-2026-129474 | Engine use-after-free in magic-method backtraces | PHP 8.5 only. Exception arguments are kept (zend.exception_ignore_args=0) with fatal_error_backtraces=1 (the 8.5 default), and a fatal error occurs when entering __call() or __callStatic(). php.ini-production sets zend.exception_ignore_args=On, but installs with no php.ini leave it Off. PHP confirms code execution in a chain that needs known memory addresses. (The underlying flaw exists in 8.2–8.4 without a known remote trigger.) |

<h2>Other vulnerabilities fixed in the release</h2>

| **CVE** | **CVSS** | **Issue and condition** |
| --- | --- | --- |
| CVE-2026-129291 | 8.8 | PHP-FPM epoll use-after-free: local privilege escalation from an FPM worker to the FPM master, which often runs as root |
| CVE-2026-127960 | 8.7 | Denial of service: folded HTTP response headers from a malicious remote server cause excessive CPU use |
| CVE-2026-128064 | 8.2 | Mixed-case HTTPS:// and FTPS:// URLs make stream wrappers send data in plaintext |
| CVE-2026-128090 | 7.7 | Phar OpenSSL signature bypass by algorithm downgrade. The attacker needs write access to a signed Phar |
| CVE-2026-129538 | 6.9 | PHP-CGI out-of-bounds read and write during PATH_INFO correction, with inconsistent path mapping on the legacy CGI binary |
| CVE-2026-129501 | 6.3 | DOM double free during XML serialization (saveXml() on manipulated input) |
| CVE-2026-15353 | 6.3 | SOAP information disclosure through malformed array dimensions |
| CVE-2026-129506 | 6.3 | SOAP use-after-free when processing DTD entity references on exposed SOAP endpoints |
| CVE-2026-129438 | 6.3 | URI extension serializes oversized input incorrectly under RFC 3986 |
| CVE-2026-129292 | 5.3 | PHP-FPM status page XSS, triggered when an operator views the full status page in a browser |
| CVE-2026-48841 | Not scored | Bundled uriparser library upgraded to 1.0.3 (fixes an integer overflow in ComposeQueryEngine; PHP 8.5.13 and 8.6.0) |

<h2>Why version checks miss PHP exposure</h2>

- **Exposure depends on configuration.** Session handler, shared session stores, FastCGI connection reuse, the build type and 8.5 settings all decide which CVEs apply. A version string shows none of them.
- **October’s patch level is not safe.** A query that treats 8.5.12, 8.4.27, 8.3.36 or 8.2.35 as fixed will miss all of these CVEs.
- **Backports hide fixes.** Distribution packages may keep old version numbers, so check the package changelog for the CVE IDs, and rebuild container images that bundle PHP.

Map findings by CVE ID, and use configuration to prioritize. Start with the FPM smuggling bug, which needs no gadget chain, then session-heavy applications.

<h2>How to find phpAfterShell and PHP Critical RCE exposure with ArmorCode</h2>

<h3>1. Ask Anya</h3>

Start with Anya, ArmorCode’s AI security champion, where you can ask targeted questions such as:

- *Which production assets are exposed to CVE-2026-126714 or CVE-2026-129289?”*
- *Show all internet-facing apps affected by the seven Critical PHP CVEs from November 2026.*
- *Am I affected by phpAfterShell Vulnerability?.*

<h3>2. Findings Page</h3>

For your ease, we have divided the saved views into two parts so you can triage both the headline flaw and the broader RCE blast radius across your environment:

- **phpAfterShell Nov 2026:** A dedicated view targeting CVE-2026-126714 so you can immediately isolate workloads exposed to the file-based session handling flaw.
- **PHP Critical RCE Nov 2026:** A broader view tracking all seven Critical CVEs in this release. Some provide direct code execution paths (such as CVE-2026-129289) while others are indirect pathways requiring gadget chains, memory address leaks, or specific runtime conditions—either way, each contributes to overall RCE risk and needs configuration-aware triage.

> **Tracking the entire November 2026 PHP release**: If you want to monitor all 18 CVEs fixed in this release (including High, Medium, and the bundled uriparser update) rather than just the seven Critical flaws, use the following filter query on the Findings page:
>
>
>
> cve IN (‘CVE-2026-129289’, ‘CVE-2026-126714’, ‘CVE-2026-115560’, ‘CVE-2026-129496’, ‘CVE-2026-129481’, ‘CVE-2026-129474’, ‘CVE-2026-129182’, ‘CVE-2026-129291’, ‘CVE-2026-127960’, ‘CVE-2026-128064’, ‘CVE-2026-128090’, ‘CVE-2026-129538’, ‘CVE-2026-129501’, ‘CVE-2026-15353’, ‘CVE-2026-129506’, ‘CVE-2026-129438’, ‘CVE-2026-129292’, ‘CVE-2026-48841’) AND status NOT IN (‘Mitigated’)

<h2>How to fix phpAfterShell and the other PHP Critical CVEs</h2>

1. **Upgrade** to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (or 8.6.0), rebuild images, and restart PHP-FPM and the web server so the patched binary loads.
2. **Turn off FastCGI connection reuse until patched.** Set fastcgi_keep_conn off in nginx or enablereuse=off in Apache, including front ends on other hosts or containers. Some images ship with reuse enabled.
3. **Harden sessions.** Set session.upload_progress.enabled=0 in php.ini or the pool config, not with ini_set(), and restart workers. Search configs for an explicit value of 1. List which apps, pools, vhosts and CLI jobs share each session store, and align their serializers. This does not fully close phpAfterShell, so still upgrade.
4. **On PHP 8.5,** set fatal_error_backtraces=0 and zend.exception_ignore_args=On.
5. **Clear startup warnings** that log to a file-based error_log, or send PHP errors to syslog, then restart the PHP master process and all workers.
6. **Plan for end-of-life PHP.** 8.1 and earlier get no upstream fix, and 8.2 reaches end of life on December 31, 2026.
7. **Watch for compromise.** Researchers report that smuggling attempts left PHP-FPM access-log entries with no matching front-end request, and the PHP warning File Upload Mime headers garbled. Also alert on web workers spawning shells.

**See how ArmorCode finds your exposure to phpAfterShell and the other critical PHP CVEs.** [Request a demo](https://www.armorcode.com/request-a-demo) to see how Anya, the “phpAfterShell Nov 2026” and “PHP Critical RCE Nov 2026” views and unified scanner findings show which PHP workloads are affected, and what to patch first.

<h2>Key Takeaways</h2>

- **What it is:** phpAfterShell (CVE-2026-126714) is a critical flaw in PHP’s file-based session handling, one of seven Critical CVEs fixed on November 19, 2026. Each has its own preconditions, so a server can be exposed to one and not another.
- **Who is affected:** PHP 8.2 to 8.5 before 8.2.36, 8.3.37, 8.4.28 and 8.5.13. phpAfterShell needs the default file session handler. Redis and database session stores are not affected by this specific flaw.
- **How to fix it:** Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. The October releases and the upload-progress setting do not cover all of them.
- **Interim mitigation:** Turn off FastCGI connection reuse and set session.upload_progress.enabled=0 in php.ini. This does not fully close phpAfterShell, so still upgrade.
- **How to find your exposure:** Use Anya or the “phpAfterShell Nov 2026” and “PHP Critical RCE Nov 2026” views, and map by CVE ID before prioritizing by configuration.

<h4>References</h4>

- **depthfirst:** [phpAfterShell (CVE-2026-126714)](https://depthfirst.com/phpaftershell)
- **PHP:** [PHP 8 ChangeLog](https://www.php.net/ChangeLog-8.php)
- **watchTowr:** [PHP CVE-2026-115560 FAQ](https://watchtowr.com/intelligence/php-cve-2026-115560-faq/)
- **Upwind:** [PHP Critical Vulnerabilities: Affected Versions and Mitigations](https://www.upwind.io/blog/php-critical-vulnerabilities-affected-versions-and-mitigations)
