Prepare to update PHP for multiple critical flaws

This message is intended for U-M IT staff responsible for PHP applications, web hosting, PHP-FPM, and container images that include PHP.

Summary

New PHP updates address 12 vulnerabilities, including seven rated Critical. Potential impacts of the vulnerabilities include remote code execution (RCE), memory corruption, denial of service, and privilege escalation, depending on which vulnerabilities are present and an application's configuration. Prepare to deploy applicable vendor-confirmed updates promptly after appropriate testing.

Note: Each of the critical vulnerabilities require non-default configurations to be present. To know if you are vulnerable you will need to check your specific PHP configuration. If one of the seven critical vulnerabilities is present, the need for immediate action supersedes the remediation timeframes in Vulnerability Management (DS-21).

Problem

Multiple flaws can affect PHP request handling, session processing, and other components. Some may permit RCE under specific application conditions; others may crash working sessions or expose memory. 

Threats

While no public exploits are known, proof-of-concept tests have shown that many of the vulnerabilities mentioned could be exploited by threat actors.

Affected Versions

Because the vulnerabilities involve a combination of unpatched versions of PHP and non-default configurations, administrators of PHP should check their installations for both. Currently, patches are available for:

  • PHP 8.2.36
  • PHP 8.3.37
  • PHP 8.4.28
  • PHP 8.5.13
  • PHP 8.6.0

Detection

Use runtime and package inventory to identify deployed PHP versions, distribution patch status, PHP-FPM/CGI usage, and relevant session configurations. Include application-specific runtimes and container images rather than checking only a default command-line installation. Review vendor advisories for per-CVE exposure and fixed packages.

Action Items

Because critical vulnerabilities require both unpatched versions and non-default configurations, the following steps are necessary:

  • Inventory PHP installations, including runtimes used by web applications, PHP-FPM pools, CGI services, command-line jobs, and deployed container images. 
  • Obtain applicable security updates from PHP or your distribution/application vendor and deploy promptly after appropriate testing, prioritizing exposed or critical services. 
  • Restart relevant PHP-FPM and web-server workers as required so updated code is loaded.
  • Verify the running version and vendor patch status afterward.

Note that users who are using existing 8.2.x, 8.3.x, 8.4.x, and 8.5.x versions of PHP are advised to update to the latest version for optimal protection.

Technical Details

Critical bugs include the possibility of an unauthenticated attacker smuggling a FastCGI request into PHP-FPM allowing RCE, a use-after-free flaw in timezone caching, a magic method backtraces vulnerability, and session handling vulnerability. The list of vulnerabilities being addressed is:

  • CVE-2026-129289 (CVSS score: 9.2) - An inconsistent interpretation of HTTP requests vulnerability that could result in execution of attacker-controlled PHP code as the worker without another user's interaction or a non-default PHP configuration. Successful exploitation requires a front end that enables persistent backend connections and an application path that opens "php://input" without reading it fully, such as nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. (Fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0)
  • CVE-2026-115560 (CVSS score: 9.2) - An improper input validation vulnerability that could result in remote code execution, file modification, session corruption, or denial-of-service. (Fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0)
  • CVE-2026-129182 (CVSS score: 9.2) - A use-after-free vulnerability that could result in memory corruption and possible full remote code execution, as in the case of CVE-2026-109619. (Fixed in PHP 8.5.13, 8.6.0)
  • CVE-2026-126714 (CVSS score: 9.2) - A Time-of-check Time-of-use (TOCTOU) vulnerability that could result in the execution of arbitrary code with the privileges of the PHP worker. Successful exploitation requires an attacker's influence over the session data, an interruption at a useful point in the write, and an application with a suitable deserialization gadget chain. (Fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0)
  • CVE-2026-129474 (CVSS score: 9.2) - A use-after-free vulnerability that could result in remote code execution on PHP 8.5 and later. Successful exploitation depends on the application and requires control over enough request data to influence memory allocation, a reachable magic method call, and a fatal error at the relevant point. (Fixed in PHP 8.5.13, 8.6.0)
  • CVE-2026-129481 (CVSS score: 9.2) - A use-after-free vulnerability that could cause an application's session cleanup to fail and potentially corrupt memory, crash a reused PHP worker, or potentially allow remote code execution. (Fixed in PHP 8.3.37, 8.4.28, 8.5.13, 8.6.0)
  • CVE-2026-129496 (CVSS score: 9.2) - A use-after-free vulnerability that could allow an unauthenticated remote attacker to crash PHP workers or execute arbitrary code with their privileges on an affected deployment. (Fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0)
  • CVE-2026-129291 (CVSS score: 8.8) - A use-after-free vulnerability that could result in local privilege escalation. Successful exploitation requires local code execution in an FPM worker, an affected pool with catch_workers_output enabled, the epoll event backend, and the ability to manipulate worker lifetimes and retain inherited pipe descriptors. (Fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0)

How We Protect U-M

ITS provides CrowdStrike Falcon to units, which should be installed on all U-M owned systems (Windows, macOS, and Linux operating systems, whether workstations or servers). Falcon administrators in ITS and in U-M units use the Falcon console to investigate and remediate issues.

Questions, Concerns, Reports

Please contact ITS Information Assurance through the ITS Service Center.