External risk intelligence

PHP Timezone Cache Use-After-Free Leads to Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-129496

This vulnerability affects PHP-FPM, Apache mod_php, and CGI workers, which are core components of web servers used to process public-facing web requests. Because these components are designed to handle incoming requests directly from the internet, the vulnerable surface is public-facing by design in normal deployments.

Use After Free

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves a critical flaw in how certain PHP components handle timing information, potentially allowing an unauthenticated attacker to execute arbitrary code on affected servers. The issue arises from a use-after-free error that can lead to a crash or, in some cases, code execution, impacting web request processing.

  • A technical flaw could allow code execution.
  • Affects critical web server components.
  • Confirm relevance and exposure to PHP deployments.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could send a crafted request to a web server running vulnerable PHP versions, targeting PHP-FPM, Apache mod_php, or CGI workers. This request would trigger a use-after-free vulnerability in the timezone cache during module startup or the first request, potentially leading to arbitrary code execution.

  • Entry condition: Publicly accessible web server.
  • Trigger point: Specially crafted incoming request.
  • Resulting risk: Remote code execution possible.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in the timezone cache could allow an unauthenticated remote attacker to crash web server workers. This could potentially lead to arbitrary code execution when triggered by specific configurations, such as diagnostics during module startup or early in a worker's first request.

  • Web server worker processes.
  • Crafted requests trigger memory access.
  • Potential for arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in PHP's timezone cache can lead to remote code execution, impacting web server components like PHP-FPM, Apache mod_php, and CGI workers. The first practical move is to identify where PHP is deployed, determine its reachability and criticality, locate the accountable owner, and then plan remediation based on risk.

  • Identify PHP deployments and ownership.
  • Verify reachability and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is PHP-FPM and how does it relate to this software?

PHP is a widely used server-side scripting language for web development. PHP-FPM, Apache mod_php, and CGI are the engine components that execute this code to generate dynamic web pages. They function by taking incoming requests from users and processing them on the server, making them essential for running modern, interactive websites.

What is a use-after-free vulnerability as seen in CVE-2026-129496?

This is a memory management flaw, specifically CWE-416. It occurs when a program continues to use a memory address after the system has already cleared or freed it. In this case, the PHP timezone cache is accidentally accessed after it has been deallocated during startup, which can confuse the program and potentially allow an attacker to hijack the execution flow.

How can an attacker trigger this CVE-2026-129496 flaw?

An unauthenticated attacker triggers this by sending a specifically crafted web request to a vulnerable server. The vulnerability requires a non-thread-safe build and is triggered during specific diagnostic events at module startup or early in a worker's first request. It does not trigger during routine operations that avoid these specific startup-time diagnostic warnings.

Why does Halo Surface Signal categorize this as an external threat?

Halo Surface Signal identifies this as an external threat because the vulnerable components—PHP-FPM, Apache mod_php, and CGI—are designed to process web traffic directly from the internet. Because these components are typically the first point of contact for public-facing web requests, they represent a significant, reachable surface for an attacker.

How should I start responding to CVE-2026-129496?

Begin by auditing your environment to map every server running PHP versions 8.2 through 8.5. Identify which of these systems are accessible from the internet versus those kept on internal networks. Once you have an inventory, prioritize patching based on the reachability and business importance of those specific web applications.

References