External risk intelligence

PHP-FPM Request Smuggling Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-129289

The vulnerability affects PHP-FPM, a component core to the deployment of public-facing web applications. While the specific exploitation scenario requires non-default backend connection reuse configurations, the affected software is ubiquitously deployed in internet-facing web server architectures, making the vulnerable surface area a common component of public web application stacks.

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 concerns a vulnerability in PHP-FPM that allows an unauthenticated remote attacker to potentially execute arbitrary code by crafting a malicious request. The issue arises from how PHP-FPM handles unread HTTP request bodies when backend connections are reused, enabling an attacker to inject parameters that can lead to code execution.

  • A flaw allows a request to be split.
  • Affects widely used web application components.
  • Confirm if your web infrastructure is exposed.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending a specially crafted multipart/form-data request to a web server running PHP-FPM with specific connection reuse settings. If the server reuses backend connections and PHP-FPM has an unread HTTP request body, the leftover data can be interpreted as a new request, allowing the attacker to forge parameters and potentially execute arbitrary PHP code.

  • Requires unread request body.
  • Smuggled request bypasses security controls.
  • Code execution and request disruption.

Live Threat

Current exploitation, exposure, and threat context

When PHP-FPM does not fully read an HTTP request body, an attacker could potentially craft a request that, when the backend connection is reused by a front-end server, allows them to execute arbitrary PHP code on the server. This can occur when specific, non-default connection reuse configurations are enabled on web servers like Nginx or Apache.

  • Unauthenticated remote code execution.
  • Unread body bytes are parsed as new requests.
  • Server compromise, including disruption of services.

Operational Fix

Recommended remediation, mitigation, and detection steps

The presence of PHP-FPM in web server architectures suggests that application owners, infrastructure teams, and potentially vendor-management teams should be involved. The immediate first step is to identify all instances of the affected PHP versions, determine if they are exposed externally or handle business-critical functions, and confirm the accountable owner for each instance before planning remediation.

  • Identify affected PHP instances.
  • Verify external reachability and criticality.
  • Plan risk-based remediation.

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 function?

PHP-FPM (FastCGI Process Manager) is a specialized engine that processes dynamic PHP code for web servers. It acts as a middleman between a web server like Nginx or Apache and the PHP interpreter, efficiently managing how requests are executed. It is a critical component in many modern web stacks, enabling servers to handle complex web applications by managing process pools that translate incoming HTTP traffic into dynamic content.

What is the weakness class behind CVE-2026-129289?

This vulnerability involves Request Smuggling, categorized as CWE-444, alongside CWE-670 regarding the improper handling of state transitions. In simple terms, the software fails to properly clear out residual data from a previous request. Because the connection is kept alive, the system mistakenly treats that leftover data as the start of a brand-new command, allowing an attacker to inject unauthorized instructions.

How does an attacker trigger this PHP-FPM flaw?

The attack requires a specific combination of conditions: the server must be configured to reuse connections between the front-end and back-end, and the application must open the request input without reading it entirely. If these settings are absent, the issue does not occur. Simply having a standard, default server setup is typically not enough to trigger this exploit.

How does Halo Surface Signal assess this risk?

Halo Surface Signal flags this as a likely risk because PHP-FPM is a core component in many public-facing web architectures. While the specific exploit needs non-default connection reuse settings, the ubiquity of PHP-FPM in internet-facing environments creates a broad potential footprint, making it important to verify whether your specific infrastructure utilizes those connection-reuse configurations.

What steps should I take to address this advisory?

First, conduct an inventory to identify all systems running the affected PHP versions (8.2, 8.3, 8.4, and 8.5 branches). Prioritize these based on whether they are internet-facing or handle sensitive business data. Once identified, consult the official vendor guidance to plan updates or patch management, focusing on confirming which instances are actually utilizing the specific backend connection reuse settings that make this vulnerability possible.

References