NEW PHP FLAW TARGETS FILE UPLOAD TRACKING
A remote code execution path in PHP’s session upload progress feature needs an unusual setup, but it is open to anyone when that setup exists. The latest PHP releases do not fix it, and a public proof of concept is out. What it means for every industry that runs PHP, and what to do now.
Published 19 November 2026, CVE-2026-115560, 9 pages, Mitigata Threat Research
In plain words
A flaw in a popular programming language that many websites are built with lets a stranger take control of a web server, but only when the site is set up one particular way. There is no fix yet, but turning off one setting now blocks the attack. The full update is due on 19 November 2026.
For business leaders
A PHP flaw, CVE-2026-115560, can let an unauthenticated attacker run code on a web server, but only where three conditions all hold. PHP has not scored it, and the 21 October releases do not fix it. A public proof of concept exists, and no in-the-wild exploitation is reported. Ask your teams to confirm this week that no application changes the session serializer at runtime and that upload progress is off on every host. Ask whether vendors bundling PHP will issue fixes, and who will install the 19 November release. Under CERT-In rules, an incident must be reported within 6 hours, so decide now who makes that call.
For security analysts
CVE-2026-115560; CWE-502. Upload progress writes PHP_SESSION_UPLOAD_PROGRESS as php_serialize; the app reads the session as php, which splits at the first pipe, so attacker text parses as a serialized object. Exploitable only when all three hold: session.serialize_handler is php_binary or php_serialize in config; code switches it to php via ini_set() before session_start(), including vendor/; session.upload_progress.enabled is on. Unauthenticated; attacker races parallel multipart uploads. Impact: code execution if gadget classes exist. Affected versions, score, fixed release: not stated; fix due 19 November 2026. 21 October releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) do not fix it. Public PoC and Docker lab on php:8.4.27-apache; not in CISA KEV; no in-the-wild exploitation reported. Step 1: set session.upload_progress.enabled = 0 in php.ini and FPM pools; keep any PHP2Shell setting. Step 2: grep ini_set.*session.serialize_handler across app and vendor/, or lock the handler in FPM with php_admin_value. Step 3: install the fixed release, rebuild images.
Key points
- PHP's session upload progress feature has an unfixed remote code execution path, CVE-2026-115560, that needs three conditions to be met.
- The 21 October PHP releases do not fix this flaw, and the fix is due in the regular release on 19 November 2026.
- Turning off session.upload_progress.enabled blocks the path now, though progress bars that read the session will stop working.
- Teams should check every application and vendor library for runtime changes to the session serializer.
- A public proof of concept exists, but no in-the-wild exploitation is reported and the flaw is not in CISA KEV.
- Alerts should watch for upload bursts and for upload progress values containing a pipe or serialized object text.
CVE ids covered: CVE-2026-109618, CVE-2026-109619, CVE-2026-115560
The full report is a PDF that opens with a work email.