External risk intelligence

PHP Session Serializer Mismatch Vulnerability Allows Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-115560

The vulnerability involves the PHP session handling mechanism during multipart file uploads. Since PHP is a widely used server-side scripting language for web applications, and file upload functionality is a common feature exposed to the public internet in many web applications, the vulnerable code path is frequently reachable in typical internet-facing deployments.

Deserialization

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 details a critical vulnerability in PHP's session handling that could allow remote code execution. When file upload progress is enabled, an attacker can inject malicious data into session keys. If these sessions are later processed by a PHP application with a different serializer, the injected data could be used to execute code on the server, cause session corruption, or lead to a denial-of-service condition. The main concern is confirming relevance and exposure due to the widespread use of PHP.

  • Session data handling flaw allows code injection.
  • Widely used web technology makes it a broad concern.
  • Assess exposure; this could impact web application integrity.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by submitting a specially crafted multipart upload to a web application. If the application's session handling is configured to use different serializer handlers for writing and reading session data, or if the handler changes at runtime, the attacker's input could be deserialized with a different handler. This could lead to the execution of arbitrary code on the server or cause session data corruption.

  • Attacker uploads data via multipart form.
  • Session deserialization mismatch occurs.
  • Potential for code execution or session corruption.

Live Threat

Current exploitation, exposure, and threat context

A mismatch in how PHP sessions are serialized could allow an attacker to execute code remotely when file upload progress is enabled. This occurs if an attacker-controlled session key is later read using a different serializer, potentially injecting malicious objects that lead to code execution or session corruption.

  • Session data and application logic.
  • Malicious data injected during upload.
  • Remote code execution or denial of service.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability arises from a mismatch in PHP's session serializers, potentially allowing remote code execution. The first practical step involves identifying all instances of the affected PHP versions, assessing their exposure and business criticality, and then determining the accountable owner for remediation.

  • Identify affected PHP installations.
  • Verify session serializer configurations.
  • Plan remediation based on exposure.

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 and how does it handle sessions?

PHP is a server-side scripting language used to build dynamic websites and web applications. It uses session management to track user state, like shopping carts or login status, by storing data on the server. The PHP engine handles this by serializing data—converting it into a stored format—and later deserializing it back into memory when the user returns.

What does CVE-2026-115560 mean by deserialization vulnerability?

This CVE involves a weakness known as Deserialization of Untrusted Data (CWE-502) and Improper Input Validation (CWE-20). It occurs because PHP can use different methods to package session data. If a session is saved using one method but read back using another, the engine may misinterpret the data, allowing an attacker to inject hidden objects that the application then executes unintentionally.

How is this vulnerability triggered?

An attacker triggers this by sending a crafted multipart file upload to the server while session upload progress is enabled. It does not occur if upload progress is disabled or if the application consistently uses the same session serializer for both writing and reading data throughout the entire session lifecycle.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal identifies this as a likely risk because PHP file upload features are standard in many web applications exposed to the public internet. If your server is internet-facing and uses the affected PHP versions, the vulnerable code path is frequently reachable by remote attackers.

What are the first steps to address this issue?

Begin by auditing your environment to inventory all instances running affected PHP versions. Once identified, review your application configurations to see how session serializers are handled. Consult the official security advisory to confirm if your specific implementation relies on the vulnerable upload progress mechanism, then prioritize updating your PHP environment.

References