Skip to content
PHP fixes 17 security flaws; four allow code execution

PHP fixes 17 security flaws; four allow code execution

Heise.De • November 19, 2026

Four weeks after the furor over the “php2shell” vulnerabilities, the team behind the open-source scripting language has released an update for four version branches. It fixes 17 security flaws, four of them critical and capable of enabling malicious code execution. Admins should update their PHP installations.

Some of the most critical flaws (all rated 9.2/10 on CVSS, “ critical ”) allow attackers to execute code under certain conditions (remote code execution).

CVE-2026-129289 : If PHP-FPM or LSAPI is configured with the FCGI_KEEP_CONN=1 parameter (default: 0), an HTTP connection is not fully cleaned up before the PHP-FPM worker accepts the request. Attackers can therefore inject their own code by forcing PHP to include it. However, this requires a PHP script on the targeted server to accept input through php://input.

CVE-2026-115560 : PHP’s “Session Upload Progress” feature allows attacker-controlled data to be written to a session in a particular serialization format and later read back using another format. A mismatched decoder can interpret part of a session key as serialized object data. Prerequisite: A PHP script must set the session handler to “php” before starting a session, and “Session Upload Progress” must be enabled.

CVE-2026-129496 : A use-after-free flaw in the time zone data cache can cause memory corruption and crash the PHP process, but it could also allow code execution. Several prerequisites apply; for example, a file-based protocol must be used. So far, code execution has only been demonstrated with known memory addresses, meaning protections such as ASLR must be bypassed.

CVE-2026-129474 : On PHP 8.5 and later, an attacker can trigger access to already-freed memory without logging in by sending a specially crafted request that causes a “fatal error”. The faulty memory access occurs while PHP collects the arguments of methods called through __call() and __callStatic() to construct a stack trace for debugging. The use-after-free can enable arbitrary code execution. The fatal_error_backtraces=1 and zend.exception_ignore_args=0 configuration settings must be enabled.

CVE-2026-129182 : In the wake of php2shell, developers found a use-after-free bug in the handling of last_fatal_error_backtrace . It can be exploited only with certain configuration settings ( max_memory_limit=1 and specific combinations of zlib.output_compression=1/0 ).

CVE-2026-126714 (9.2 " critical ")

CVE-2026-129481 (9.2 " critical ")

Ten other security flaws are rated from CVSS 8.7 (“high”) to CVSS 5.3 (“medium”):

CVE-2026-129291 (8.8 " high ")

CVE-2026-127960 (8.7 " high ")

CVE-2026-128064 (8.2 " high ")

CVE-2026-128090 (7.7 " high ")

CVE-2026-129438 (6.3 " medium ")

CVE-2026-129506 (6.3 " medium ")

CVE-2026-15353 (6.3 " medium ")

CVE-2026-129501 (6.3 " medium ")

CVE-2026-129292 (5.3 " medium ")

CVE-2026-129538 (6.9 " medium ")

Although there are some recommendations for mitigating the critical security flaws, updating to the PHP version in use is a more lasting solution. The patched versions are:

The updated PHP versions are available to download from the project website . Updates are also available for Linux distributions such as Debian; Debian’s update is version 8.4.28-1~deb13u1, for example. Admins should promptly bring their PHP installations up to date.

On Dec. 3, heise is holding an online conference on PHP security, bettercode() PHP 2026 . Volker Dusch, release manager for the current PHP version, and other experts will offer practical guidance on securing PHP applications and servers running PHP for the future.

This article was originally published in German . It was translated with technical assistance and editorially reviewed before publication.