Skip to content

+Threat Wire · Reference

phpAfterShell and six other PHP critical flaws

PHP published 17 security advisories on November 19, 2026, including seven critical flaws such as phpAfterShell; several can lead to code execution in specific configurations.

Prioritize patchingCVE-2026-126714CVE-2026-129289CVE-2026-115560+8 moreChecked Nov 19

What it means for your AI agents

Agent backends, MCP servers and webhook receivers are usually built on these runtimes and libraries. A flaw that runs code before authentication hands an attacker the agent's keys and tool access, not just the server.

  • Check the services behind your agents and MCP tools, including ones that only call outward.
  • Look for the affected component in dependencies too, not just the runtime you installed directly.
  • Until patched, treat output from an affected service as untrusted input to your agents.

Updates

  • Nov 19, 2026 : PHP released 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0 with fixes for 17 security advisories, and depthfirst published its phpAfterShell research .

Details

On November 19, 2026, PHP released 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0 with fixes for 17 security advisories: seven rated critical (CVSS v4.0 9.2), four high and six medium. This briefing covers the seven critical flaws. In its advance notice, PHP said the critical issues require either non-default configuration or uncommon setups.

phpAfterShell (CVE-2026-126714) is in PHP's default file-based session handler. If a session write is interrupted, the file can keep the start of the new session and the end of the old one. The next session_start() can then deserialize objects an attacker placed there. Session upload progress is one way for a remote client to shape the stored data, and applications that store large user-controlled strings in sessions are another. PHP's advisory says code execution also needs an interruption at a useful point and a suitable deserialization gadget chain in the application.

depthfirst says it discovered and reported phpAfterShell; the CVE record credits Leo Lin and Asahi as reporters. depthfirst reports that it reached code execution without an application gadget class by chaining a second, undisclosed memory corruption bug in a PHP-native class. The sources reviewed do not establish whether that second bug is fixed in these releases.

CVE-2026-129289 lets an unauthenticated attacker smuggle a second FastCGI request into PHP-FPM and run PHP code as the worker. PHP says this needs a front end that reuses backend connections, such as nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on or HAProxy, and an application path that opens php://input without reading it to the end. The demonstrated attack also needs the path of an existing PHP script. Front ends that close the FastCGI connection after each request are not affected by it. LSAPI shares the cleanup bug, but PHP does not establish code execution there.

CVE-2026-115560, the session serializer mismatch covered in the php2shell briefing, is now fixed, and the fix turns session upload progress off by default. PHP's November 19 advisory widens its scope: no runtime serializer change is needed when separate applications, pools or command-line jobs with different serializers share a session store. CVE-2026-129481 is a use-after-free in PHP 8.3 and later that PHP describes as an incomplete fix for CVE-2026-109619; PHP has not demonstrated code execution through it.

CVE-2026-129496 is a use-after-free in non-thread-safe builds. An unauthenticated attacker can crash a fresh worker, and possibly run code, when a startup diagnostic has been written to a PHP error log file. PHP's advisory says code execution was demonstrated locally in PHP-FPM and Apache mod_php with known memory addresses.

CVE-2026-129474 and CVE-2026-129182 are use-after-free bugs in fatal error backtraces, which PHP 8.5 enables by default. Both affect PHP 8.5, and PHP says CVE-2026-129474 also affects later versions. For CVE-2026-129474, PHP notes that the zend.exception_ignore_args=1 setting in php.ini-production blocks the demonstrated attack path. CVE-2026-129182 also needs specific path-level settings and an Apache per-directory configuration or front end that produces an early diagnostic. PHP has not demonstrated code execution through it.

On November 19, 2026, none of the 17 vulnerabilities was in CISA's Known Exploited Vulnerabilities catalog, and no source reviewed reports exploitation in the wild. CISA does list CVE-2026-109618 and CVE-2026-109619 from the October php2shell release. Two of today's critical fixes, for CVE-2026-129481 and CVE-2026-129182, close gaps left by the fix for CVE-2026-109619.

Risk

No source reviewed on November 19, 2026 reports exploitation in the wild. PHP says phpAfterShell affects its default session handler; CVE-2026-129289 allows unauthenticated code execution with FastCGI connection reuse.

Affected deployments

PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13. PHP 8.6.0 contains all 17 fixes; depthfirst and PHP confirm that 8.6.0 release candidates were affected by phpAfterShell and CVE-2026-129474. Whether a deployment is exposed depends on the conditions of each flaw, described in the details.

PHP 8.1 and earlier are end of life. depthfirst says the official 7.4, 8.0 and 8.1 end-of-life mitigation branches are not affected by phpAfterShell. PHP's advisories say CVE-2026-129289 was introduced in PHP 5.6.0 and that releases older than 8.2 may also be affected by CVE-2026-115560.

Distribution packages can backport fixes without changing the PHP version number, so check the full package version against the distribution's advisory.

Evidence and sources18 links

PHP security advisories

The 17 advisories published on November 19, 2026, with affected versions, conditions and mitigations.

GHSA-fm2m-fjf5-v3cp: partially overwritten session files (phpAfterShell) (CVE-2026-126714)

GHSA-qc49-hpvq-g2w6: PHP-FPM request smuggling (CVE-2026-129289)

GHSA-658j-r8rw-q6mx: session serializer mismatch (CVE-2026-115560)

GHSA-gr4f-wgx5-jpfv: timezone cache use-after-free (CVE-2026-129496)

GHSA-g3vh-838c-65v7: use-after-free after interrupted session shutdown (CVE-2026-129481)

GHSA-8mjj-2r7p-4hg2: use-after-free in magic method backtraces (CVE-2026-129474)

GHSA-2fjv-p558-g82m: use-after-free in fatal error backtrace (CVE-2026-129182)

All php-src security advisories

PHP release announcements

Advance notice of November 18, 2026 and the five releases of November 19, 2026.

Advance notice

PHP 8.2.36

PHP 8.3.37

PHP 8.4.28

PHP 8.5.13

PHP 8.6.0

PHP 8 ChangeLog

Lists the fixes in each release with their GHSA and CVE identifiers.

PHP 8 ChangeLog

depthfirst: phpAfterShell

Research by depthfirst, which says it discovered CVE-2026-126714, with its affected versions and mitigation. depthfirst says it withheld the native code execution chain.

depthfirst: phpAfterShell

depthfirst: technical analysis

CISA Known Exploited Vulnerabilities catalog

None of the 17 vulnerabilities was listed in catalog version 2026.11.18, checked on November 19, 2026.

CISA KEV catalog

Check your exposure with an agent

Paste this into an AI agent that can see your infrastructure. It asks for a read-only check of what's affected, including the systems behind your agents, and a table you can act on. Copying it changes nothing.

Prompt
Assess whether the infrastructure you can access is affected by phpAfterShell and six other PHP critical flaws (CVE-2026-126714, CVE-2026-129289, CVE-2026-115560, CVE-2026-129481, CVE-2026-109619, CVE-2026-129496, CVE-2026-129474, CVE-2026-129182, CVE-2026-109618, CVE-2026-15353 and CVE-2026-129506). Work read-only within your authorized access: do not run exploits, change configuration, restart services or install anything.

1. Confirm the affected and fixed versions from the vendor advisories and CVE records:
   - https://www.php.net/ChangeLog-8.php
   - https://www.php.net/archive/2026.php#2026-11-19-2
   - https://www.php.net/archive/2026.php#2026-11-19-3
   - https://www.php.net/archive/2026.php#2026-11-19-4
   - https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx
   - https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
   Cite each source and the date you read it. Say plainly what you could not verify.

2. Inventory the systems that could run the affected software, including the hosts, containers, MCP servers, tool runners and sandboxes behind any AI agents. For each, record the asset, environment, owner if known and the version actually running, from read-only evidence (package metadata, version commands, platform inventory).

3. Note which affected systems are reachable from the internet or from agents and tools, and which credentials (model-provider keys, tool tokens, service accounts) are stored on them.

4. Report one row per asset: asset, running version, affected (yes / no / unknown), reachable from, credentials at risk, evidence, and the next step. List anything you could not access as a gap rather than assuming it is safe.

More from the Threat Wire

Briefing source: Cloudflare Radar Zero Wire (Cloudforce One), last checked November 19, 2026. Refreshed here every 30 minutes.