External risk intelligence

PHP Magic Method Backtrace Use-After-Free Memory Corruption

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-129474

The vulnerability affects PHP, a language engine fundamentally designed to process incoming web requests. Because PHP is widely deployed as the backend for public-facing web applications and API endpoints, it is highly probable that vulnerable instances are reachable via the public internet.

Use After Free

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a critical vulnerability in PHP related to how it handles certain method calls during error reporting. If specific configurations are enabled and a fatal error occurs, an attacker could potentially corrupt memory or even execute arbitrary code. The primary concern is confirming if affected PHP versions and configurations are in use.

  • Memory errors could allow code execution.
  • Affects PHP; confirm relevance and exposure.
  • Understand potential, verify your use.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending crafted requests that influence memory allocation within a PHP application. If a fatal error occurs during specific method calls, and certain PHP configuration settings are active, the attacker might trigger memory corruption. This could lead to a denial-of-service condition or, under specific circumstances, allow for arbitrary code execution.

  • Entry condition: Attacker controls request data.
  • Trigger point: Fatal error during magic method calls.
  • Resulting risk: Remote code execution or crash.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in PHP's magic method backtraces could allow a remote attacker to cause memory corruption, crash the PHP worker, or execute arbitrary code when specific error conditions occur and configuration settings are not optimized for security. This could happen when PHP attempts to capture arguments during a method call that has already had its memory freed, particularly if a fatal error happens simultaneously.

  • PHP worker memory.
  • Memory corruption via crafted requests.
  • Remote code execution or service crash.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability, found in PHP's handling of method call backtraces, could allow remote code execution under specific conditions, particularly when error handling configurations are not hardened. Identifying affected PHP installations, understanding their reachability, and confirming business criticality are the crucial first steps. The primary responsibility likely lies with teams managing the application infrastructure and development teams responsible for the PHP code itself.

  • Identify and assess PHP deployments.
  • Confirm application owner and criticality.
  • Plan remediation based on 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 the PHP software mentioned in CVE-2026-129474?

PHP is a popular server-side scripting language used to power dynamic websites, content management systems, and backend web APIs. It functions as an engine that processes code on a web server to generate the HTML or data sent to a user's browser. This specific vulnerability involves how the engine manages memory during error reporting for certain types of method calls.

How does this use-after-free vulnerability work?

This is a memory management error categorized as CWE-416. It occurs when the engine tries to access memory that has already been released. In this case, when PHP generates a backtrace during a fatal error, it may mistakenly reference stale memory locations from a previous method call. If an attacker can manipulate the request data to influence these memory operations, it can lead to instability or unauthorized code execution.

What triggers this vulnerability in PHP?

An attacker must be able to send crafted request data that forces the application into a fatal error, such as hitting a memory limit, while specifically invoking magic methods like __call() or __callStatic(). The issue does not occur if the PHP configuration includes zend.exception_ignore_args, which is standard in production environments, as this setting prevents the engine from attempting to include the vulnerable argument data in backtraces.

How do I know if my systems are relevant to this threat?

Halo Surface Signal indicates that because PHP is the core engine for public-facing web applications, vulnerable instances are frequently reachable from the internet. You should care if you are running PHP versions 8.5.0 through 8.5.12, especially if your configuration has disabled the protective zend.exception_ignore_args setting or is not using the default production configuration.

What should I do to address CVE-2026-129474?

Begin by inventorying your environment to locate all running instances of PHP 8.5 series. Verify if your specific application configurations have zend.exception_ignore_args set to enabled, as this acts as a critical safeguard. Coordinate with your development or infrastructure teams to plan for updating to a patched version once available, and prioritize applications that are directly accessible from the public internet.

References