24 Oct 2026
CVE-2026-115560 in PHP: What Website Owners Need to Know
Two days after the PHP2Shell patches, PHP disclosed a separate, still-unpatched vulnerability tied to session upload-progress handling.
Two days after PHP shipped emergency patches for the critical PHP2Shell vulnerabilities, PHP’s security team disclosed a separate issue — now tracked as CVE-2026-115560 — on 23 October 2026. Unlike PHP2Shell, this one was not accompanied by a same-day fix: as of this review, PHP has published an advisory and a mitigation, but not a patched release.
This article explains what’s actually confirmed about CVE-2026-115560, what remains uncertain, and what PHP itself recommends doing about it right now. If you haven’t already read our PHP2Shell advisory covering CVE-2026-109618 and CVE-2026-109619, that’s the more urgent, already-patchable issue — read that one first if you haven’t patched yet.
Last reviewed: 24 October 2026. PHP has stated a fix is planned for its next regular release cycle rather than an emergency patch, so the status described here may change — check php.net’s security page directly before treating any detail here as current.
Why this is a separate story from PHP2Shell
It’s easy to assume a second PHP vulnerability disclosed within the same week is “more of the same” — it isn’t, and conflating the two leads to the wrong response. The two situations differ in several important ways:
| PHP2Shell (CVE-2026-109618 / -109619) | CVE-2026-115560 | |
|---|---|---|
| Disclosed | 20–21 October 2026 | 23 October 2026 |
| Patch available | Yes — same-day emergency release | No — PHP has not named a fix date or version |
| Who’s affected | Any PHP install actively serving web requests | Applications using a specific, non-default session configuration pattern |
| PHP’s own severity framing | Critical, CVSS v4.0 9.2 | Framed by PHP as unlikely to be exploited in practice |
| Authentication required | No | Depends on application-specific configuration conditions |
What’s confirmed about CVE-2026-115560
- PHP published an informational advisory on 23 October 2026, stating that a full advisory with complete technical details would follow with the project’s next routine release, rather than as an emergency out-of-cycle patch.
- The issue again involves PHP’s session-handling subsystem, specifically session upload-progress tracking combined with how the session serialization handler is configured — the same general area implicated (though not confirmed) in the PHP2Shell leak.
- Multiple outlets reporting on PHP’s own guidance describe the trigger conditions as requiring an application to set
session.serialize_handlertophp_binaryorphp_serialize, and then change it tophpat runtime usingini_set(), before callingsession_start(). This is a specific, non-default configuration pattern — most applications never touchsession.serialize_handlerprogrammatically at all, let alone switch it mid-request. - PHP’s recommended interim mitigation is the same configuration change suggested for part of the PHP2Shell issue: disabling session upload-progress tracking entirely, via
session.upload_progress.enabled = 0. - As of this review, no affected-version range, fixed-version number, or official CVSS score had been published by PHP for this specific CVE.
- No confirmed exploitation of CVE-2026-115560 had been reported by major vendors as of this review, in contrast to the exploitation attempts vendors reported against PHP2Shell within hours of its leak.
What’s still unclear or unconfirmed
- The exact technical root cause beyond “session upload-progress handling, interacting with session serialization handler reconfiguration.”
- Which specific PHP versions are affected — some secondary reporting suggests the issue may be present even in the just-patched 8.5.12 release, but this has not been confirmed in an official PHP advisory as of this review.
- A confirmed patch version or release date — PHP has indicated this will arrive with a routine release rather than an emergency one, which by itself signals PHP’s own assessment that this does not carry PHP2Shell-level urgency.
Treat anything beyond the points above — including any specific CVSS score or affected-version list you may see cited elsewhere — as unverified until it appears on PHP’s own security advisory page.
Does this affect you?
This is the key practical question, and the honest answer for most site owners is: probably not directly, but it’s worth five minutes to check.
The documented trigger requires your application’s code to explicitly call ini_set('session.serialize_handler', 'php') at runtime, after having a different handler (php_binary or php_serialize) configured, before starting a session. This is unusual — the large majority of PHP applications, including most installations of WordPress, Laravel, and similar frameworks, never programmatically touch this setting.
If you have custom-built PHP code, or a developer who can check for you, the practical question to ask is: “Does any of our code call ini_set() on session.serialize_handler at runtime?” If the answer is no, the documented trigger path for this specific CVE doesn’t apply to your application as currently understood — though that understanding may be incomplete until PHP’s full advisory ships.
Recommended action right now
- Apply the mitigation PHP recommends regardless: set
session.upload_progress.enabled = 0in your PHP configuration and restart your PHP workers (PHP-FPM, Apache, etc.) for the change to take effect. This is a low-risk configuration change — session upload-progress tracking is a feature most sites never rely on — and PHP recommends it as the interim step while a dedicated fix is pending. - If you run internet-facing infrastructure that handles sensitive data, the Canadian Centre for Cyber Security’s broader guidance around this period has recommended considering network isolation for exposed systems until confirmed patching is complete — a more conservative stance worth considering for genuinely high-value targets, even though PHP’s own severity framing is lower for this specific issue.
- Ask your developer or host directly whether your application touches
session.serialize_handlerprogrammatically, rather than guessing. - Watch for PHP’s full advisory with the next routine release, which should confirm affected versions, a fixed version, and a formal severity rating. Revisit this page or php.net directly once that lands.
- Don’t let this distract from PHP2Shell. If you haven’t yet confirmed your PHP version is patched to 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 (or later), that remains the more urgent, more broadly applicable, already-fixable issue.
What patching this would — and wouldn’t — prove
There’s no patch to install yet for this specific CVE, so the relevant question right now isn’t “did we patch” but “did we apply the recommended configuration mitigation, and do we understand whether the trigger conditions apply to our own code.” Once PHP ships a real fix, the same caveat from our PHP2Shell coverage applies here too: patching closes the vulnerability going forward, but doesn’t retroactively tell you whether anything happened before you patched.
What this article is not
This is an informational advisory for business decision-makers and website operators, not a substitute for PHP’s own official advisory, which will contain the complete technical detail once published. It contains no exploit code or attack instructions, and nothing here should be tested against any system you don’t own or have explicit written authorization to test.
Key takeaways
CVE-2026-115560 is a real, separately-disclosed PHP issue identified two days after the PHP2Shell patches, with no official fix yet as of this review, and a narrower set of documented trigger conditions than PHP2Shell. PHP itself frames the practical risk as unlikely for most applications, but recommends disabling session upload-progress tracking as a precaution while a permanent fix is pending. The single highest-value action for most readers is still making sure PHP2Shell is patched — this is a smaller, secondary item to track alongside that, not a reason to deprioritize it.
Shahid Security’s Vulnerability Assessment service includes reviewing exactly this kind of platform-level configuration exposure as part of a broader security review, not just scanning for known CVEs.
Want a second opinion on whether your PHP configuration is actually exposed to either of these issues? Email info@shahidiqbal.com or book a free consultation.
Sources: The Hacker News — PHP Warns of Another Unpatched RCE Risk Two Days After Emergency PHP2Shell Patches, Astra Security — CVE-2026-115560: Another PHP Session-Handler RCE, SecureWorld — PHP2Shell Isn’t Over: New Unpatched RCE Flaw Surfaces, The Back Room Tech — PHP shares mitigation for new RCE vulnerability without patch, Brandefense — PHP Upload Progress RCE: What to Do Now. For the authoritative, continuously updated technical record, check php.net’s own security advisories directly.
FAQ
Is CVE-2026-115560 the same vulnerability as PHP2Shell?
No. PHP2Shell refers specifically to CVE-2026-109618 and CVE-2026-109619, which were patched in emergency releases on 21 October 2026. CVE-2026-115560 is a separate, newly disclosed issue made public two days later, and — as of this review — has no official patch yet.
Do I need to update PHP again if I already patched for PHP2Shell?
The 21 October releases (PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35) do not fix CVE-2026-115560 — it was identified afterward and PHP has not yet shipped a dedicated fix. Patching for PHP2Shell was still necessary and correct; it simply doesn't cover this separate issue.
Should I panic about this one the way I did about PHP2Shell?
Not based on what's confirmed so far. PHP's own advisory frames the practical risk as unlikely, since exploitation depends on an application specifically reconfiguring its session serialization handler at runtime in an unusual way — a configuration most applications don't use. That said, 'unlikely for most' is not the same as 'irrelevant to everyone,' so it's still worth the five minutes to check your own configuration.

Written by Shahid Iqbal
Founder & Cybersecurity Consultant, Shahid Security
