PHP Session Vulnerability: CVE-2026-126714 and CVE-2026-115560 Can Lead to Remote Code Execution, Fixed in PHP 8.5.13, and What to Check This Week
PHP has fixed two session flaws, CVE-2026-126714 and CVE-2026-115560, that can lead to remote code execution. Here is what is confirmed, what is not, and what to check on your servers this week.
Where Worldwide
On this page 8 sections
PHP has fixed two flaws in its session handling that can lead to remote code execution, which means an attacker could run their own commands on your web server. If your website, online store or web app runs on PHP, the fixed release is 8.5.13. One of the two flaws was also demonstrated on PHP 8.2.35, 8.3.36 and 8.4.27 builds.
The flaws are tracked as CVE-2026-126714 and CVE-2026-115560. Both sit in ext-session, the part of PHP that saves session data and reads it back. Session data is what a site keeps between page loads, such as who is logged in.
What happened with the PHP session vulnerability
The official PHP 8 changelog entry for Version 8.5.13 lists two security fixes:
- CVE-2026-126714 (GHSA-fm2m-fjf5-v3cp): "Partially overwritten session files can lead to remote code execution"
- CVE-2026-115560 (GHSA-658j-r8rw-q6mx): "Session serializer mismatch can lead to remote code execution"
The first advisory was published on the PHP project's GitHub page by bukka on November 19, 2026. It lists the affected versions as 8.5.0 and later, up to but not including 8.5.13.
The second advisory covers a mismatch between the way session data is written and the way it is read back. According to that advisory, the report behind it includes command execution using a Guzzle object gadget on PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Command execution was also reproduced with a Monolog 2.11.1 gadget, using a php_serialize writer and a php reader.
If you read our earlier post on PHP2Shell, these are separate CVE numbers with their own advisories. The sources we used do not say whether they are connected to that earlier issue, so we are not making that link.
What is confirmed and what is not known
Confirmed on PHP's own pages:
- PHP 8.5.13 fixes both CVE-2026-126714 and CVE-2026-115560.
- CVE-2026-126714 affects PHP 8.5.0 up to, but not including, 8.5.13.
- The serializer mismatch report demonstrated command execution on PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.
- The serializer mismatch advisory says: "Keeping the feature disabled removes the upload-progress attack path described in this advisory."
Not known from the sources we checked:
- Whether either flaw is being used in real attacks. The advisories describe demonstrations in a report, not attacks on live sites.
- The fixed versions for PHP branches other than 8.5.13. Our sources name only 8.5.13.
- The full list of affected versions for CVE-2026-115560, beyond the builds where it was demonstrated.
- Who found the flaws. The material we reviewed does not name the researchers.
How serious are CVE-2026-126714 and CVE-2026-115560?
Each advisory gives a CVSS 4.0 rating. In plain terms:
| What the rating covers | CVE-2026-126714 | CVE-2026-115560 |
|---|---|---|
| Can be attacked over the network | Yes | Yes |
| Attack complexity | Low | High |
| Needs certain conditions on the target | Yes | Yes |
| Attacker needs a login | No | No |
| Needs someone to click something | No | No |
| Impact on data, changes and uptime | High | High |
In practice, an attacker needs no account and no help from a user, but the target has to be set up a certain way for the attack to work. So the configuration checks below matter as well as the update. The full ratings are CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N for CVE-2026-126714 and CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N for CVE-2026-115560.
What is an object gadget, and do Guzzle and Monolog need patching?
PHP stores session data in a serialized form and turns it back into PHP values when a visitor returns. If an attacker can shape that stored data, PHP may rebuild objects from code that is already installed on the server. Those pieces of existing code are called gadgets. The report used gadgets from Guzzle and from Monolog 2.11.1 to turn the session flaws into command execution.
The advisories place the flaws in PHP's ext-session, and the fix is PHP 8.5.13. The sources we checked do not list a fix for Guzzle or Monolog, so the update that matters here is PHP itself.
What to do this week
| Step | What to do | How to check |
|---|---|---|
| 1 | Find every server and hosting account that runs PHP | List your websites, online stores, customer portals and internal tools, then ask your host or developer which PHP version each one uses |
| 2 | Update to PHP 8.5.13 | After the update, confirm the version the site actually reports, for example with php -v on the server or in your hosting control panel |
| 3 | On other PHP branches, find your version's fix | Check the official PHP 8 changelog or ask your host. Our sources did not confirm fixed versions for these branches |
| 4 | Keep the session upload-progress feature disabled | The serializer mismatch advisory says keeping it disabled removes the upload-progress attack path it describes |
| 5 | Check for a session serializer mismatch | Ask your developer whether anything writes sessions with php_serialize and reads them with php, the combination used in the report |
| 6 | Ask vendors about software they run for you | For any app or site a vendor hosts, ask which PHP version it runs and when they will move to a fixed release |
Disabling the upload-progress feature does not replace the update. The advisory says it removes one attack path, not that it fixes both flaws.
Why this matters for a business website
A flaw that lets an outsider run commands on your web server puts the whole site at risk, not just one page. Both ratings list high impact on the data on the system, on whether that data can be changed, and on whether the system stays up. Customer records, form submissions and the site itself could all be exposed to whoever gets in.
PHP may also run underneath software you bought instead of built, such as an app a vendor hosts for you. If you do not control the server, you depend on someone else to install 8.5.13. Our posts on who is patching your servers and on why updated is not the same as patched explain how to get a straight answer from a vendor.
PHP session vulnerability questions people are asking
Which PHP version fixes the session vulnerability?
PHP 8.5.13. The official PHP 8 changelog lists both CVE-2026-126714 and CVE-2026-115560 as fixed in that release.
Which PHP versions are affected?
CVE-2026-126714 affects PHP 8.5.0 up to, but not including, 8.5.13. For CVE-2026-115560, the report demonstrated command execution on PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. We did not find a full affected range for it.
Is the PHP session flaw being exploited in attacks?
We don't know. The advisories describe command execution shown in a report, not attacks on real sites. Treat it as urgent anyway, because a working method has been demonstrated.
Is there a fix for other PHP branches?
Our sources do not confirm one. Check the official PHP changelog for your branch, or ask your host what they are installing.
Does an attacker need a password?
No. Both CVSS ratings list no privileges and no user interaction. The server does have to meet certain conditions for the attack to work.
Can I turn something off instead of updating?
The serializer mismatch advisory says keeping the upload-progress feature disabled removes the upload-progress attack path. That covers one path only, so update to a fixed release as well.
What do CVE-2026-126714 and CVE-2026-115560 mean in plain English?
The first is about session files that are partly overwritten. The second is about session data written in one format and read back in another. PHP's advisories say both can lead to remote code execution.
The bigger lesson
Keeping a website patched means more than updating the plugin or app you can see. The language it runs on needs updates too. For every server you rely on, including the ones a host or vendor runs for you, someone has to own that job.
Want someone to check your servers? See security hardening or request a quote.
Get security alerts like this by email, with the free checklist, at security alerts.
Sources: PHP 8 ChangeLog; PHP advisory GHSA-fm2m-fjf5-v3cp; PHP advisory GHSA-658j-r8rw-q6mx.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Linux KVM Vulnerability CVE-2026-99312: AMD Hosts With Nested Virtualization Affected, What Is Confirmed and How to Check Yours
A Linux kernel flaw in the KVM hypervisor, CVE-2026-99312, affects hosts with AMD processors and nested virtua...
PHP Critical Vulnerability: Seven RCE Flaws Fixed in PHP 8.5.13 and 8.6.0, Which Version to Install for Your Branch and Who Is Exposed
PHP's 19 November 2026 security releases fix seven critical remote code execution flaws. Here is which version...
F5 BIG-IP Vulnerability: Critical No-Login Flaws in APM and iRules Can Crash TMM, No Workaround, and the Emergency Hotfixes to Install
F5 shipped emergency hotfixes for critical BIG-IP APM and iRules flaws that let attackers with no login crash...