PHP session RCE via upload progress
High risk · public exploit
Risk assessment
PHP before 8.2.36/8.3.37/8.4.28/8.5.13 lets remote attackers inject objects into sessions, risking RCE (CVSS 9.2). Update now.
What to do
Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.
- No fixed version listed yet. Restrict exposure and watch the vendor advisory. NVD references
- Remediation in this advisory
Exploitation confirmed - public proof-of-concept - CVE-2026-115560 is a critical remote code execution issue in PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28, and 8.5.* before 8.5.13 that lets an unauthenticated attacker inject serialized objects into a victim’s session by submitting a multipart file upload. Patched releases are available; update immediately.
Overview
PHP’s session upload progress feature, when enabled, stores metadata about an in-flight file upload under a key in the user’s session. The serializer used to write that session data depends on the session.serialize_handler setting, which can be php_binary, php_serialize, or the legacy php format.
The problem appears when the same session data is written with one handler and later read with another. That can happen if session.serialize_handler is changed at runtime, or if two applications share a session store but use different serializer settings. Data written under php_binary or php_serialize may contain raw bytes that, when reinterpreted by the php serializer, get passed straight into PHP’s unserializer.
Because the upload progress key contains attacker-controlled filename data, an attacker who can submit a multipart upload controls part of those bytes. If the reading application loads a class with a usable gadget chain, this turns into remote code execution. Even without a gadget chain, attackers can corrupt session state or trigger denial of service.
Impact
The CVSS score is 9.2. Attackers need no credentials and no user interaction, though the attack complexity is rated high because successful exploitation depends on a serializer mismatch and, for code execution, the presence of a suitable gadget chain in the reading application. Realistic targets are multi-tenant hosts, shared session backends such as Redis or Memcached, and applications that switch serializers between requests. Sessions may also be silently corrupted, logging users out or breaking application state.
Remediation
Update PHP to 8.2.36, 8.3.37, 8.4.28, or 8.5.13 depending on your branch. If you cannot patch immediately:
- Disable
session.upload_progress.enabledif the feature is unused. - Ensure every application sharing a session store uses the same
session.serialize_handler. - Avoid changing the serializer at runtime.
- Do not use the legacy
phpserializer; preferphp_serialize.
Restrict upload endpoints where feasible, and monitor for unexpected object injection errors in logs. Breach and incident context is available in our breach reports and security news.
Security Insight
This bug is a textbook example of serializer confusion, the same class of mistake behind the long history of PHP object injection flaws. What makes it notable is that it lives in PHP’s own session machinery, not in userland code, and it only manifests under configuration drift, which is exactly the kind of gray area that patch cycles miss. Shared session stores and per-application serializer overrides are common in sprawling PHP estates, so this fix deserves inventory work alongside the version bump.
Further Reading
Exploit references 9 PoC Show
Public PoC References
Unverified third-party code
These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).
Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.
| Repository | Stars |
|---|---|
| sykeops/CVE-2026-115560 PHP Session upload progress RCE - CVE-2026-115560 | ★ 8 |
| googlesky/CVE-2026-115560 PoC and Docker lab for CVE-2026-115560 — PHP session upload-progress serialize_handler mismatch to unauthenticated object injection / RCE. Validated end-to-end on php:8.4.27-apache with mitigation and | ★ 3 |
| prnjlksingh/php-cve-2026-115560-demo | ★ 2 |
| basesixtythree/B63-POC-CVE-2026-115560 PoC and verification material for CVE-2026-115560 (PHP session serializer confusion via session.upload_progress -> object injection -> RCE) | ★ 1 |
| ivst/CVE-2026-115560 CVE-2026-115560: PHP session upload progress mitigation | ★ 1 |
Showing 5 of 9 known references. Source: nomi-sec/PoC-in-GitHub.
Get a Telegram alert when the next one lands: PHP advisories