Skip to content
PHP Timezone Cache Vulnerability Enables Remote Code Execution

PHP Timezone Cache Vulnerability Enables Remote Code Execution

First seen 19 Nov 2026, 16:15 UTC • • •Early signal · one source

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 19, 2026 at 16:16 UTC
  • •PHP's timezone cache vulnerability can lead to remote code execution.
  • •Attackers can exploit this flaw via crafted HTTP requests under specific configurations.
  • •A patch has been released, but the vulnerability poses a significant risk if not addressed.

An use-after-free vulnerability in PHP's timezone cache can lead to remote code execution. This flaw occurs during process startup when PHP retains a reference to a freed timezone cache, allowing attackers to trigger memory corruption and potentially execute arbitrary code. Affected configurations include non-thread-safe builds where diagnostics written to error logs can access freed memory. Exploitation can occur via crafted HTTP requests, particularly under certain configurations like FPM and Apache mod_php. The vulnerability has been confirmed to allow native command execution under specific conditions. PHP workers can inherit the stale reference from parent processes, creating a vulnerable window until the first normal request is completed. The issue has been reproduced with various configurations, and while a patch is available, the potential for exploitation remains. The vulnerability is classified as CVE-2026-XXXX, with no known reported yet.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-19
Vulnerability disclosed
PHP disclosed a use-after-free vulnerability in the timezone cache that can lead to remote code execution.
Github

More articles in this cluster (1)

Common questions

What versions of PHP are affected?
The vulnerability affects PHP configurations that are non-thread-safe and utilize the timezone cache.
Is there a patch available?
Yes, PHP has released a patch to address the vulnerability.
What should I do if I'm using PHP?
Update to the latest version of PHP to mitigate the risk associated with this vulnerability.