PHP Session Vulnerability CVE-2026-115560: Critical Serializer Flaw Can Lead to Remote Code Execution, the Fixed Versions and the Setting to Disable
PHP has fixed CVE-2026-115560, a critical session serializer flaw that can lead to remote code execution. Here are the fixed versions, the setting to turn off until you upgrade, and what is still not known.
Where Worldwide
On this page 8 sections
PHP has fixed a critical security flaw, CVE-2026-115560, in the way it writes and reads session data. The PHP project's own advisory says it can lead to remote code execution, which means an attacker could run commands on your web server. If your website, online store, customer portal or internal tool runs on PHP, the fix is an upgrade to 8.2.36, 8.3.37, 8.4.28 or 8.5.13, and there is one setting to turn off until you can.
We have written about PHP security before, in PHP2Shell Vulnerability: What It Is and How to Fix It and Updated Is Not the Same as Patched. This post covers only what the PHP project has published about CVE-2026-115560 and what a business should do about it this week.
What happened with CVE-2026-115560
PHP's official ChangeLog describes the fix like this: "Fixed GHSA-658j-r8rw-q6mx (Session serializer mismatch can lead to remote code execution). (CVE-2026-115560)". GHSA-658j-r8rw-q6mx is the security advisory the PHP project published on its GitHub repository. It has the most detail, and it is where the affected versions below come from.
The PHP news archive announced the release ahead of time and scheduled it for Thursday, 19 November 2026, between 14:00 and 14:30 UTC. It called these releases part of PHP's regular four-week release cycle and said they "will address security vulnerabilities affecting all supported PHP versions." The same announcement says: "The highest severity is CRITICAL."
Which PHP versions are affected by CVE-2026-115560
| PHP branch | Affected versions (per the advisory) | Upgrade to |
|---|---|---|
| 8.5 | 8.5.0 and later, below 8.5.13 | 8.5.13 or later |
| 8.4.0 | 8.4.0 and later, below 8.4.28 | 8.4.28 or later |
| 8.3.0 | 8.3.0 and later, below 8.3.37 | 8.3.37 or later |
| Below 8.2.36 | Every version below 8.2.36 | 8.2.36 or later |
Look at the last row. The advisory's first range has no lower limit, so it counts every version below 8.2.36 as affected, older branches included. It lists no separate fixed version for anything older than 8.2.36. If you run an older branch, the lowest fixed version in the advisory is 8.2.36, so you have to move up a branch.
For the newest branch, PHP's announcement is direct: "All PHP 8.5 users are encouraged to upgrade to this version."
How serious is the PHP session flaw? Confirmed vs not known
Confirmed by the primary sources:
- PHP rates the highest severity in this release as CRITICAL.
- The advisory gives a CVSS v4 vector of
AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. In plain terms, the attack works over the network, needs no login and needs no click from a user. If it succeeds, the damage to confidentiality, integrity and availability is high. The vector also rates attack complexity as high and says certain conditions must be present, so not every PHP server is automatically exploitable. - The advisory says: "Command execution was also reproduced with a Monolog 2.11.1 gadget using a
php_serializewriter and aphpreader."
Not known from the sources we read:
- Whether attackers are exploiting it. The advisory describes a reproduction, and that is not the same as attacks in the wild. None of the sources we used report exploitation.
- A single severity score. We have the vector but no numeric score.
- How many setups are exposed. The reproduction used one specific writer and reader combination. Our sources do not say how common that combination is. You may see reports putting a number on how many websites are at risk. None of the primary sources we used gives that figure.
What is a PHP session serializer mismatch?
PHP sessions are how a website remembers a visitor from one page to the next: who is logged in, what is in the cart, which admin is signed in. PHP saves that data to a session store between requests. Before saving, it converts the data to text (serializing). When reading it back, it converts the text back again.
The advisory names two of the formats PHP can use, php_serialize and php. According to the advisory title, a mismatch between how session data is written and how it is read can lead to remote code execution. In the reproduction, data was written in one format and read in the other. Combined with a gadget, meaning code already inside an installed library that attacker-supplied data can trigger, this produced command execution.
What to do this week
- List every PHP install. Include live sites, staging copies, internal tools and older servers people have forgotten about.
- Check the version the web server actually runs. Running
php -von the command line can show a different PHP version from the one serving your site. Confirm it through a phpinfo page you remove afterwards, or through your host's control panel. - Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 or later, depending on your branch. If you are below 8.2.36, plan a move to a newer branch.
- If you cannot upgrade yet, set
session.upload_progress.enabled=0in every configuration that can write to the affected session store. That is the advisory's interim step. - Set it at the server level, not in code. The advisory is clear: "Calling
ini_set()from the application is too late." - Check shared session stores. If several apps or servers write to the same session store, every one of them needs the setting or the upgrade.
- Ask your host or vendor in writing which exact PHP version is running, and when it will reach a fixed version.
- Restart PHP services after upgrading and check the version again.
Why the PHP session flaw matters for a business website
Sessions sit right next to the most sensitive parts of a website: customer logins, checkout and the admin area. A flaw that can lead to remote code execution on the web server is a flaw that could put all of that within an attacker's reach. That includes the database, stored customer details and the site itself.
The harder question for many businesses is who owns the upgrade. A PHP version often sits under a hosting plan, a vendor's application or a server set up years ago. If nobody can tell you within a day which PHP version each site runs, that gap is the real risk. Our post Who Is Patching the Software That Runs Your Business? covers how to close it.
PHP session vulnerability questions people are asking
Is CVE-2026-115560 being exploited?
Not as far as the sources we read say. The advisory describes command execution reproduced in testing, and none of our primary sources reports attacks in the wild.
Which PHP version fixes CVE-2026-115560?
According to the advisory's affected ranges: 8.2.36, 8.3.37, 8.4.28 and 8.5.13, or anything later on the same branch.
I run an older PHP branch. Am I affected?
The advisory lists every version below 8.2.36 as affected and gives no fixed version for older branches. Plan a move to a fixed version on a newer branch.
Can I turn off upload progress from my application code?
No. The advisory says calling ini_set() from the application is too late. Set session.upload_progress.enabled=0 in the server configuration, in every configuration that can write to the affected session store.
How bad is the PHP RCE bug?
PHP rates the release's highest severity as CRITICAL. The CVSS vector shows no login and no user interaction, but high attack complexity and specific conditions.
My host manages PHP. Do I still need to do anything?
Yes. Ask the host for the exact version in writing. A note saying the server is up to date does not tell you whether it runs a fixed build.
The bigger lesson
PHP ships on a regular four-week cycle, and this release shows why that cycle matters: a critical fix can land on any given Thursday. Patching is a routine, not a one-off emergency. Every business running PHP needs a named person who knows each server's version and applies the fix within days.
See how we harden and maintain servers at /tech/security-hardening, or get a quote for help.
Get security alerts like this by email, with our free checklist, at /security-alerts.
Sources: PHP security advisory GHSA-658j-r8rw-q6mx; PHP 8 ChangeLog; PHP news archive 2026.
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...
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....