PHP disclosed CVE-2026-129496, a timezone-cache flaw that can corrupt memory before application code handles a request. Update the deployed PHP runtime and restart its processes. Exposure depends on startup diagnostics and PHP’s file-based error logging, so the configuration matters alongside the version.

The advisory was published November 19. PHP’s release announcements confirm that the four repaired releases are available. This is a distinct flaw from the October PHP2Shell vulnerabilities; those earlier repairs do not replace today’s update.

A startup warning can outlive the memory it used

PHP formats file-log timestamps with the configured timezone. In a non-thread-safe build, a startup diagnostic can create a timezone cache in temporary memory. Startup then frees that memory while retaining a reference to it.

A diagnostic during early request initialization can use the stale reference before the date extension resets it. That is a use-after-free, access to memory whose lifetime has ended. Request data may already occupy the released space.

The advisory identifies these exposure conditions:

  • A suitable startup warning or deprecation, emitted late enough that later initialization leaves the cache reference intact. An invalid timezone setting is one confirmed example.
  • PHP writes that diagnostic through its file-based error_log path. PHP-FPM’s own error log alone does not meet this condition.
  • An early diagnostic reaches a fresh worker before its first normal request completes. Parent processes can pass the stale reference to FPM or Apache workers. Newly created and recycled workers can encounter the condition again.

The issue has also been reproduced with CGI. The advisory’s detailed mechanism concerns non-thread-safe builds; it does not establish an identical exposure for every PHP deployment mode.

Crashes and code execution have different demonstrated conditions

Evidence status: controlled demonstrations described by PHP, with no in-the-wild campaign identified in the reviewed sources. A crafted HTTP request crashed an FPM worker under ordinary nginx header limits and the default input-variable limit.

Local demonstrations also achieved native command execution in FPM and Apache mod_php, using known runtime addresses and additional configuration or memory-layout assumptions. The advisory says a remote address-randomization bypass is plausible, but an independent complete bypass has not been demonstrated.

Those qualifications limit the published demonstrations. They do not make worker crashes harmless or establish that other code-execution paths are impossible.

Apply the repair for the deployed branch

The advisory and PHP changelog identify these upstream repairs:

PHP branch Affected upstream versions Fixed release
8.2 8.2.0 through versions below 8.2.36 8.2.36
8.3 8.3.0 through versions below 8.3.37 8.3.37
8.4 8.4.0 through versions below 8.4.28 8.4.28
8.5 8.5.0 through versions below 8.5.13 8.5.13

The fix uses UTC for log timestamps outside a fully initialized active request. It avoids using request-local timezone state at unsafe lifecycle points.

For distribution packages, confirm the distributor’s repaired build rather than judging a backport solely by its upstream version string. Rebuild application images that bundle PHP, and verify the runtime serving requests after restarting.

Temporary controls must remove the startup trigger

Until the update is deployed, PHP recommends correcting settings that produce startup warnings or deprecations, then restarting the master process and all workers. A suitable logging destination such as syslog avoids the demonstrated file-timestamp path. Preserve the ability to collect operational logs when changing destinations.

Changing cookie handling or $_REQUEST settings is incomplete mitigation. The demonstrated Apache cleanup path does not require those settings. Address the documented startup and logging conditions while arranging the runtime update.

Caveat: The advisory demonstrates memory corruption and conditional local code execution; it supplies neither a complete remote exploit nor a count of compromised deployments.