Executive Summary

On November 19th, 2026, the PHP project released security updates for all supported branches alongside its PHP 8.6.0 feature release, fixing 18 vulnerabilities. Seven are rated critical and reachable remotely without authentication. The most practical, CVE-2026-129289, lets an attacker smuggle a request into the PHP FastCGI Process Manager (PHP-FPM) to run PHP code on the server. Two others, CVE-2026-115560 and CVE-2026-129474, can also lead to remote code execution.

PHP, the runtime behind many internet-facing web applications, reports that CVE-2026-129289 can let an unauthenticated attacker run their own PHP code on a server. According to PHP, the attack requires two conditions present: a front end that keeps its connections to PHP-FPM open between requests, and an application that opens the request body without reading all of it. That connection reuse is off by default in nginx and Apache, according to their documentation, and Caddy's default setup opens a new connection for every request limiting practical impact for these setups. Additional information is available in the Technical Details section of this advisory.

No exploitation has been reported at the time of writing, but public proof-of-concept (PoC) exploits for CVE-2026-115560 report code execution against lab environment targets. Organizations that updated for the recent "PHP2Shell" campaign with specific configurations remain affected by the recently disclosed vulnerabilities. Given remote reach, public PoC code, and exploitation attempts of last month's related "PHP2Shell" flaws, Beazley Security recommends affected organizations apply available fixes as soon as possible.

Affected Systems or Products

CVE

Product

Affected Versions

Fixed Versions

CVE-2026-129289

PHP (PHP-FPM)

8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13

8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0

CVE-2026-129474

PHP (Engine)

8.5 before 8.5.13

8.5.13, 8.6.0

CVE-2026-115560

PHP (Session extension)

8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13

8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0

CVE-2026-129496

PHP (Date extension)

8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13

8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0

CVE-2026-126714

PHP (Session extension)

8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13

8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0

CVE-2026-129182

PHP (Engine)

8.5 before 8.5.13

8.5.13, 8.6.0

CVE-2026-129481

PHP (Session extension)

8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13

8.3.37, 8.4.28, 8.5.13, 8.6.0

Mitigations / Workarounds

The PHP project released an official update bundule for these vulnerabilities in PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36, and fixes every critical issue that affects its branch.

If patching cannot be immediately applied, the following may help to temporarily reduce risk on specific builds and configurations within PHP. These interim steps do not cover every vulnerability in the release. :

  • Disable FastCGI connection reuse between the front end and PHP-FPM. Remove fastcgi_keep_conn on in nginx and enablereuse=on in Apache mod_proxy_fcgi, and configure HAProxy FastCGI backends to close the connection after each request. This removes the precondition for CVE-2026-129289.

  • PHP provides guidance for CVE-2026-115560 where configurations are able to write to an affected session store. Set session.upload_progress.enabled=0 and restart PHP workers.

  • On PHP 8.5 affected by CVE-2026-129474, PHP recommends confirming that zend.exception_ignore_args=1 is set, and to restart workers after changing it.

  • Correct PHP startup warnings that are written to a file-based error log, such as an invalid date.timezone value. Exploiting CVE-2026-129496 depends on them.

  • Make sure PHP-FPM and LSAPI listeners cannot be reached from untrusted networks.

Also note, PHP 8.2 reaches end of life on December 31st, 2026, and official fixes will cover supported branches only.

Patches

The PHP project published the fixed releases on November 19th, 2026, with details in the PHP 8 ChangeLog. Please note that distribution and hosting provider builds may carry the fixes without changing the upstream version number, so check the provider's security notice.

Technical Details

PHP-FPM

CVE-2026-129289 is a request smuggling flaw in how PHP handles a request body that it reads lazily. When an application opens php://input and does not read it to the end, PHP treats the body as handled at request shutdown. It then skips the normal cleanup that discards unread input. If a front end keeps the FastCGI connection open for reuse, PHP-FPM parses the leftover bytes as a new FastCGI request. This is a logic flaw rather than memory corruption, so the attacker does not need to know memory addresses. No public PoC is known at the time of writing.

With a single crafted multipart/form-data request, an unauthenticated attacker can forge a backend request with chosen parameters, including SCRIPT_FILENAME, REMOTE_ADDR, and PHP_ADMIN_VALUE. The forged request bypasses front-end routing and runs attacker-controlled PHP code with the privileges of the worker.

By default, nginx, Apache and Caddy do not keep FastCGI connections open, but HAProxy does. Affected front ends include nginx if configured with fastcgi_keep_conn on, Apache mod_proxy_fcgi if configured with enablereuse=on, and HAProxy FastCGI configurations that keep backend connections open. Organizations should check their own configurations to confirm.

PHP Engine

CVE-2026-129474 affects only PHP 8.5. When PHP collects the arguments of a call handled by __call() or __callStatic() for a backtrace, it can read stale values that point to freed memory. The trigger is a fatal error, such as exceeding memory_limit, at the moment the application enters such a call. An attacker who controls enough request data to influence memory allocation can then corrupt memory or crash the worker. With knowledge of memory addresses, the attacker can execute code.

The flaw requires fatal_error_backtraces to be enabled, which is the default on 8.5, and

zend.exception_ignore_args

to be disabled. PHP's php.ini-production file enables

zend.exception_ignore_args

which blocks the attack. PHP states that it confirmed remote code execution on PHP 8.5, and that exploitation depends on the application reaching a magic method call.

CVE-2026-129182 also affects only PHP 8.5. A fatal error raised while modified INI settings are restored at request shutdown can repopulate the stored fatal error backtrace after the executor has been cleaned up. A diagnostic emitted early in a later request on the same PHP-FPM or mod_php worker then reads the stale backtrace. The shutdown error requires per-path configuration of max_memory_limit, or of zlib.output_compression together with output_handler (which .user.ini can set). The early diagnostic requires Apache per-directory configuration, or a PHP_VALUE or PHP_ADMIN_VALUE parameter sent by the front end. PHP describes this CVE as further scenarios for the stale global state problem behind CVE-2026-109619. Code execution has not been demonstrated.

Session Extension

CVE-2026-115560 is a session serializer mismatch. When session upload progress is enabled, it stores attacker-controlled upload data in a session key using the php_binary or php_serialize serializer. Suppose the same session is later read with the php serializer, because session.serialize_handler changes at runtime or differs between applications that share a session store. Bytes inside the key then reach the unserializer.

An attacker who can submit a multipart upload can inject objects this way. This leads to code execution when the reading application contains a suitable gadget chain, or otherwise to session corruption or denial of service. PHP's report includes command execution using a Guzzle object gadget. PHP first disclosed the issue in an informational advisory on October 23rd, 2026, two days after the PHP2Shell fixes, and the November releases deliver the full fix. Public GitHub repositories, including googlesky/CVE-2026-115560 and basesixtythree/B63-POC-CVE-2026-115560, publish PoC exploits that achieve command execution against intentionally vulnerable Docker lab applications with the required serializer mismatch and gadget class in place.

CVE-2026-126714 stems from the default files save handler, which writes updated session data into the existing session file without clearing it first. An interrupted write can leave a file that holds the start of the new session followed by the end of the old one. The application later accepts that file when it calls session_start(), and bytes of an ordinary string can then be unserialized as objects. The security firm depthfirst disclosed the flaw, which it calls "phpAfterShell", on November 19th, 2026. Its researchers reached the vulnerable code through session upload progress, which runs before the application does, so an application login check does not block it. They demonstrated remote code execution by combining the flaw with a separate memory corruption flaw in a built-in PHP class. The October PHP2Shell fix restricted object creation during upload progress processing, but this attack takes a different path. Depthfirst states that applications that store sessions in Redis or a database instead of PHP's file handler are not affected.

CVE-2026-129481 affects PHP 8.3 through 8.5, and PHP 8.2 is not affected. The session extension records the filename of the executing script when a session starts. A fatal error in an application callback while session variables are destroyed at shutdown, such as stream_close() in a user-defined stream wrapper, leaves that pointer in place after request memory is freed. A later request on the same worker then frees the stale string. The flaw requires the filename to sit in request memory, for example when OPcache does not cache the script. PHP describes it as an incomplete fix for CVE-2026-109619. It can crash workers or corrupt memory, but code execution has not been demonstrated.

Date Extension

CVE-2026-129496 affects non-thread-safe builds. If a diagnostic is written to a file-based error_log during module startup, the timezone cache is allocated in startup memory that is later freed while a reference to it remains. An invalid date.timezone value or a session configuration warning can produce such a diagnostic. A diagnostic raised early in a worker's first request, such as the max_input_vars warning, then accesses the freed cache. On such a deployment, an unauthenticated remote attacker can crash PHP-FPM, Apache mod_php, or CGI workers with a crafted request. PHP has demonstrated code execution when memory addresses are known.

Related "PHP2Shell" Exploitation

In October 2026, PHP fixed CVE-2026-109618 and CVE-2026-109619, known together as "PHP2Shell", in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Both flaws allow unauthenticated remote code execution on affected web servers. CISA added both to its KEV catalog in October after attacks were reported. The October releases do not contain these November fixes and a server patched for PHP2Shell, with affected configurations remains exposed to the vulnerabilities in this advisory until it applies the latest fixes.

How Beazley Security is responding

Beazley Security is monitoring client perimeter devices through our Exposure Management Platform to identify impacted devices and support organizations in remediation of any issues found.

We are also conducting threat hunts across our MDR environment to detect potential exploitation attempts against our clients.

If you believe your organization may have been impacted by these vulnerabilities and need support, please contact our Incident Response team.