On this page (9 sections)
The PHP project shipped its regular four-week security release on November 19, 2026, fixing seven critical-severity vulnerabilities. One of them, CVE-2026-115560, is a session serializer mismatch in upload progress tracking that can lead to remote code execution under a specific combination of configuration and code.
If you run PHP on a web server, a shared host or a container image, you should plan to upgrade to a fixed release. Until you can, a documented mitigation is available for this particular flaw. Note that the research behind this article rests on press reporting and the CVE record; we could not find the original PHP advisory text, so details below are attributed to those sources.
At a glance
What happened
According to SecurityWeek, PHP maintainers announced the November 19 release ahead of time, saying it would address vulnerabilities affecting all supported PHP versions, with a highest severity of Critical, and that some were reachable only in non-default configurations or uncommon setups. CVE-2026-115560 was publicly disclosed about two days after the earlier PHP2Shell vulnerabilities made headlines, and PHP recommended a mitigation while waiting for the patch.
When the release landed, The Hacker News reported that it fixes seven critical flaws, six rated CVSS 9.2 and one rated 8.8, with outcomes that include remote code execution, memory corruption, denial of service and local privilege escalation.
How CVE-2026-115560 works
PHP stores session data using a serializer, a format for turning data into text. The setting session.serialize_handler chooses the format. The weakness class here is unsafe deserialization (CWE-502): if a program reads attacker-influenced bytes with a serializer that can rebuild objects, the attacker may be able to create objects the application never intended.
Per the CVE record, session upload progress can store attacker-controlled data in a session key when the php_binary or php_serialize serializer is used. If that same session is later read with the php serializer, bytes inside the key can reach the unserializer. That can happen when the handler is changed at runtime, or when applications sharing a session store use different handlers. A remote attacker who can submit a multipart upload could then inject objects. Code execution is possible only if the reading application contains a suitable gadget chain; otherwise the outcome may be session corruption or denial of service.
PHP's maintainers, quoted by SecurityWeek, described the trigger as an unusual combination: an application sets session.serialize_handler to php_binary or php_serialize, switches it to php at runtime with ini_set() before calling session_start(), and session upload progress is still enabled.
The other six flaws in the same release
The same release carries six more critical fixes, so upgrading matters even if your setup does not match the condition above. As summarized by The Hacker News:
| CVE | CVSS | Type | Fixed in |
|---|---|---|---|
| CVE-2026-129182 | 9.2 | Use-after-free | 8.5.13, 8.6.0 |
| CVE-2026-126714 | 9.2 | TOCTOU in session writes (named phpAfterShell by Depthfirst) | 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129289 | 9.2 | Inconsistent HTTP request interpretation with persistent backend connections | 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129474 | 9.2 | Use-after-free, PHP 8.5 and later | 8.5.13, 8.6.0 |
| CVE-2026-129481 | 9.2 | Use-after-free in session cleanup | 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129496 | 9.2 | Use-after-free, unauthenticated | 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129291 | 8.8 | Use-after-free, local privilege escalation in FPM | 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
Who is realistically exposed
- Servers on PHP 8.2, 8.3, 8.4 or 8.5 below the fixed versions listed above.
- Applications that enable session upload progress and either change session.serialize_handler at runtime or share a session store with another application that uses a different handler.
- Sites with a deserialization gadget chain in their code or libraries, which turns object injection into code execution. This is common in large frameworks and plugin ecosystems, so do not assume you have none.
- Shared and managed hosting, where several applications may share session storage.
For context, SecurityWeek notes that the earlier PHP2Shell vulnerabilities were widely exploited, with attacks beginning days before patches were published. The sources do not report exploitation of CVE-2026-115560, but that history is a good reason not to delay.
How to check your exposure
First find your PHP version. Run this on the server, and repeat it for the PHP-FPM or Apache module version if they differ from the command line build. Compare the result with the fixed versions above.
php -vNext, check whether session upload progress is on. This prints the effective value for the command line PHP; web workers may use different ini files, so also review the ini files your FPM pool or Apache module loads. A value of 1 means enabled.
php -i | grep -E 'session.upload_progress.enabled|session.serialize_handler'Then search your code for runtime serializer switches, which are the trigger PHP described. Run it from your application root and review each hit.
grep -rn "serialize_handler" --include=*.php .What to do now
- Inventory every PHP runtime: host packages, FPM pools, containers and base images.
- Upgrade to a fixed release: 8.2.36, 8.3.37, 8.4.28 or 8.5.13 (or 8.6.0).
- If you cannot patch yet, disable session upload progress, the mitigation PHP recommended for this issue.
- Make sure all applications sharing a session store use the same session.serialize_handler.
- Remove runtime ini_set() switches of session.serialize_handler where you can.
- If you use persistent backend connections (fastcgi_keep_conn on, enablereuse=on), review them while patching for CVE-2026-129289.
- Restart PHP-FPM or Apache after the upgrade and confirm the new version with php -v and a phpinfo check on the web path.
- Rebuild and redeploy container images that bundle PHP; a host upgrade does not change them.
Disabling session upload progress is a php.ini setting. Set it in the ini file your workers load, then reload the service.
session.upload_progress.enabled = 0On Debian or Ubuntu, you can see which PHP packages are installed and whether your distribution has a newer build. Distributions often backport fixes without changing the upstream version number, so check your vendor's security notice rather than relying on the version string alone.
dpkg -l | grep -i phprpm -qa | grep -i phpDetection and monitoring afterwards
Look for signs of probing: unusual multipart upload requests to PHP endpoints, spikes in PHP worker crashes or restarts, and corrupted or unexpectedly large session files. Review web server error logs for fatal errors around upload handling. If you see unfamiliar PHP files, new admin users or changed files after the disclosure date, treat the site as possibly compromised and follow a website hacked response guide.
A read-only security scan can help you keep track of what your public site exposes, and outside-in malware detection has limits you should understand: it cannot see inside your server or confirm a PHP build. Patching and configuration review remain the fix.
Open questions
We could not find the original PHP advisory text in our research, so the exact wording of the maintainers' guidance comes via press reports. The sources do not report active exploitation of CVE-2026-115560 specifically, and the CVE record lists no vulnerable package names. Check the PHP project's own release notes and your distribution's security tracker for authoritative fixed package versions.
For a broader hardening baseline, see our WordPress security checklist if your PHP runs WordPress, and small business website security.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
