Skip to content
Multiple PHP vulnerabilities including remote code execution (CVE-2026-115560 ...

Multiple PHP vulnerabilities including remote code execution (CVE-2026-115560 ...

Dynatrace • November 19, 2026

On November 19, 2026, the PHP project released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. These security releases fix 17 vulnerabilities across all supported PHP branches. Seven are rated critical (CVSS v4.0 9.2). Under specific conditions, several of them can lead to remote code execution, for example CVE-2026-129289 (PHP-FPM request smuggling), CVE-2026-115560 and CVE-2026-126714 (session handling) and CVE-2026-129474 (PHP 8.5). Other issues can lead to local privilege escalation, information disclosure or denial of service.

According to PHP, the critical issues require non-default configuration or uncommon setups. For example, CVE-2026-129289 needs a web server that reuses connections to PHP-FPM, and CVE-2026-129474 and CVE-2026-129182 affect only PHP 8.5. No attacks have been reported so far. Details are in the PHP security advisories .

This release follows the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), which PHP fixed on October 21, 2026. As described in our earlier alert , those vulnerabilities did not affect Dynatrace software.

What this means for Dynatrace

OneAgent Software Bill of Materials (SBOM): OneAgent SBOMs list PHP components, because OneAgent includes PHP header files to support monitoring of the PHP versions listed in its technology support matrix . These header files are not a PHP runtime. Vulnerability scanners that match on these SBOM entries may report the PHP CVEs for OneAgent. These findings do not apply.

OneAgent compatibility: No OneAgent update is required. We are verifying OneAgent on the fixed PHP versions.

Upgrade PHP on servers, container images and CI runners, then restart all PHP workers (for example PHP-FPM pools or Apache).

Check the version used by your web workers ( php-fpm -v ), not only the command line ( php -v ), because they can differ. Don’t rely on the version string alone. Linux distributions and image vendors often backport fixes without changing it, so check your vendor’s advisory or package changelog for the CVE IDs.

Prioritize internet-facing applications and setups that match the conditions described in the critical advisories, such as PHP-FPM behind a web server that reuses FastCGI connections, applications that use different session serializers on the same session storage, or PHP 8.5 with fatal error backtraces enabled (the PHP 8.5 default).

If you cannot patch right away, check the PHP security advisories for the vulnerabilities that apply to your setup. Each advisory lists its own workarounds, for example keeping FastCGI connection reuse disabled for CVE-2026-129289, or disabling session upload progress for CVE-2026-115560 and CVE-2026-126714. A workaround only covers the vulnerability it is listed for and does not replace the update.

Check software that bundles PHP , such as content management systems or vendor appliances, and follow the vendor’s advisory.

No Dynatrace action is required. Upgrading PHP also protects applications monitored by OneAgent.

Find PHP in your environment with Dynatrace. This query lists monitored processes that run a PHP version older than the fixed releases:

The query covers processes that ran in the last 24 hours. Extend the timeframe to include PHP jobs that run less often, keeping in mind that longer timeframes also list processes that have since been replaced. The query relies on the version that PHP reports. If your distribution or image vendor backports fixes, a patched PHP can still show an older version here.