PHP2Shell reminded us that PHP powers a vast range of websites, applications, and products, often running behind the scenes in places organizations may not immediately think to look. With three new advisories now drawing attention to PHP’s internals, security teams face a familiar challenge: understanding where the runtime is deployed, how it is configured, and who can move quickly when a fix is available.
PHP’s three critical advisories point to different failure points in the runtime, from memory cleanup to session parsing. Their impact depends on the PHP version and, in some cases, how the application is configured.
|
Vulnerability |
Description |
Fixed Version / Remediation |
|---|---|---|
|
Backtrace use-after-free (CVE-2026-129474) |
When PHP records an error’s history, it can mistakenly refer to memory that has already been cleared while handling certain method calls. Under specific conditions in PHP 8.5, an attacker may be able to exploit this to run code as the PHP process. |
Upgrade to PHP 8.5.13 |
|
Timezone-cache use-after-free (CVE-2026-129496) |
A startup warning can leave PHP pointing to timezone data that is no longer in use. If another warning occurs during an early request, PHP may crash or mishandle memory; in some conditions, that could let an attacker run code as the PHP process. |
Upgrade to PHP 8.2.36, 8.3.37, 8.4.28, and 8.5.13 |
|
Session serializer mismatch (CVE-2026-115560) |
PHP can save session data in one format and later read it as another. If upload-progress tracking is enabled and the application has the right code available, an attacker may be able to turn that mismatch into code execution. |
Disable upload progress (workaround) or upgrade to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13. |
Memory-safety flaws are especially consequential in a language runtime because they can let an attacker influence how a process handles data or control flow. Here, the affected paths include backtrace generation and timezone-cache handling, which are operations that may sit outside the application code teams typically review. Under the right conditions, the outcome can range from a worker crash to code execution with the PHP worker’s privileges.
Session handling carries a different risk: the same stored data can be interpreted differently by different readers. If one component writes session data using one format and another reads it using a different format, attacker-controlled content may be treated as serialized objects. Teams should check for upload-progress settings, shared session stores, and applications or processes that use different serializers.
The fixes are available, but applying them across an organization can take more than updating a public-facing server. PHP may also run in internal services, containers, test environments, appliances, and products maintained by another vendor
Start with an inventory, then track each deployment through to a verified fix:
A patch plan is only complete when teams can confirm that affected deployments have been updated or mitigated, including less visible systems and bundled runtimes. For more on the inventory and ownership challenge, see our October analysis of PHP2Shell.