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 to install for each branch, who is most exposed and what is still not known.
Where Worldwide
On this page 9 sections
PHP has released security updates that fix seven critical-severity remote code execution flaws, bugs that, in the wrong setup, let an attacker run their own code on the server behind your website or web app. If your business runs anything built on PHP, find out which version it uses this week and move to the fixed release for that branch.
PHP's own announcement adds an important caveat: the critical issues require non-default configuration or uncommon setups. So this is not an emergency for every PHP site. It is still worth checking, because many businesses have no idea how their hosting stack is configured.
This post covers the November 2026 security release: which version to install, who is actually exposed and what the sources leave unanswered.
What happened with the PHP security release
The PHP project scheduled its security releases for Thursday, 19 November 2026, between 14:00 and 14:30 UTC. According to SecurityWeek, the release includes fixes for seven critical-severity remote code execution (RCE) vulnerabilities.
The fixes did not land the same way on every branch:
- PHP 8.6.0 and PHP 8.5.13 fix all of the critical bugs, plus 10 high and medium-severity flaws.
- PHP 8.4.28, PHP 8.3.37 and PHP 8.2.36 include patches for most of the issues, according to SecurityWeek.
The word "most" matters. If your branch's fixed release is 8.2.36, 8.3.37 or 8.4.28, it covers most of the issues but, by that account, not every one of them. The sources we checked do not list which issues were left out.
What is confirmed and what is not
Confirmed in PHP's own security advisories:
- CVE-2026-129289 (PHP-FPM). An unauthenticated attacker can make certain bytes form a separate FastCGI request, someone with no login can slip an extra request past the web server to PHP. It carries a severity score of 9.2. The affected range is PHP 8.4.0 up to, but not including, 8.4.28. Exploitation requires a front end that enables persistent backend connections.
- CVE-2026-115560. An application with a suitable object gadget chain can execute code with the privileges of the PHP worker. A public report demonstrated command execution using a Guzzle object gadget on PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12, the versions released just before this round of fixes.
Confirmed in PHP's release announcement:
- The configuration caveat. PHP's release announcement states: "The issues rated CRITICAL require either non-default configuration or uncommon setups."
Reported by SecurityWeek: the count of seven critical RCE flaws, and a description of one of them: "A mismatched decoder can interpret part of a session key as serialized object data."
Not known from the sources:
- Whether any of these flaws are being exploited in real attacks.
- The full list of all seven CVE IDs, and the exact setup each one needs.
- Which issues were not fixed in 8.4.28, 8.3.37 and 8.2.36.
- Whether branches earlier than 8.2.35 received any fix.
Am I affected by the PHP vulnerability?
The version number answers half the question. Your configuration answers the other half. You are most likely to be exposed if:
- Your server runs PHP-FPM behind a front end that keeps persistent connections open to PHP. That is the condition CVE-2026-129289 depends on.
- Your PHP-FPM or LSAPI listener can be reached from an untrusted network, such as the open internet.
- Your application includes code that could form an object gadget chain. That is the condition CVE-2026-115560 depends on, and the public demonstration used a Guzzle gadget.
Non-default or uncommon does not mean nobody. Custom hosting stacks, performance-tuned servers and setups inherited from a previous developer often stray from the defaults. If nobody on your team can say how your PHP is configured, treat yourself as possibly exposed until someone checks.
Which PHP version fixes the critical vulnerabilities
| If you run | Install | What it covers |
|---|---|---|
| The 8.5.12 branch | 8.5.13 | All critical bugs, plus 10 high and medium flaws |
| New install or major upgrade | 8.6.0 | All critical bugs, plus 10 high and medium flaws |
| The 8.4.27 branch | 8.4.28 | Most issues (8.4.0 to 8.4.27 is affected by CVE-2026-129289) |
| The 8.3.36 branch | 8.3.37 | Most issues |
| The 8.2.35 branch | 8.2.36 | Most issues |
| A branch earlier than 8.2.35 | Not stated | The sources do not mention a fix |
If you want every critical fix, 8.5.13 or 8.6.0 is the only path the sources confirm. Moving up a branch can break older application code, so test on a copy of the site first.
How to check your PHP version
- On your own server: run
php -vfor the command-line version, then check the PHP-FPM version too, since the web server and command line can use different PHP installs. - On managed or shared hosting: look in the hosting control panel for the PHP version setting, or ask your host.
- If a developer or agency runs it: ask them in writing which PHP version and branch the site is on, whether it uses PHP-FPM or LSAPI, and when they will install the fixed release.
What to do this week
- List every website, store and web app your business runs that uses PHP, including old ones.
- Record the PHP version for each one, from both the command line and PHP-FPM.
- Upgrade each one to the fixed release for its branch: 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or move to 8.6.0.
- Make sure no PHP-FPM or LSAPI listener can be reached from untrusted networks. PHP's advisory says plainly: "Do not expose PHP-FPM or LSAPI listeners directly to untrusted networks."
- Ask whoever set up the server whether the front end keeps persistent connections open to PHP-FPM.
- If your branch's fixed release is 8.2.36, 8.3.37 or 8.4.28, plan a move to 8.5.13 or 8.6.0, since those branches only got most of the fixes.
- Plan a replacement for anything on a branch earlier than 8.2.35, since the sources describe no fix for it.
Why this matters for a business website
Remote code execution turns a website problem into a server problem: code that runs with the privileges of the PHP worker can do whatever that worker is allowed to do, including reading and changing the website's own files.
The harder question for most businesses is who owns the job. Hosting companies, agencies and freelancers often assume someone else updates PHP, leaving the server on last year's version. If you host your own stack, our self-hosting and infrastructure page explains how we keep servers maintained after launch.
PHP vulnerability questions people are asking
Is the PHP vulnerability being exploited?
The sources we checked do not say. A public report demonstrated command execution for CVE-2026-115560, proving the flaw can be used, but no source reports real attacks.
Which PHP version fixes all seven critical bugs?
PHP 8.6.0 and PHP 8.5.13, according to SecurityWeek.
Is PHP 8.4.28, 8.3.37 or 8.2.36 patched?
Partly. They include patches for most of the issues, but not necessarily all of them.
What is CVE-2026-129289?
A PHP-FPM flaw, rated 9.2, that lets an unauthenticated attacker smuggle a separate FastCGI request. It affects 8.4.0 up to 8.4.28 and needs a front end with persistent backend connections.
What is CVE-2026-115560?
A flaw that lets an application with a suitable object gadget chain run code with the PHP worker's privileges. It was demonstrated on 8.2.35, 8.3.36, 8.4.27 and 8.5.12.
Does a default PHP setup need this update?
Yes, update anyway. PHP says the critical issues require non-default configuration or uncommon setups, but the release also fixes 10 high and medium flaws.
Is an older PHP branch fixed?
The sources do not mention it. Plan to move to a supported branch.
The bigger lesson
A flaw that only hits "uncommon setups" is harmless only if you know your setup. Most businesses learn their configuration the day something breaks. Keep a written record of every PHP site, its version, how PHP-FPM connects and who installs updates, and this kind of release becomes a short check instead of a scramble.
See how we lock down and maintain servers at security hardening, or request a quote for a review of your PHP sites.
Get security alerts like this by email, with our free checklist, at /security-alerts.
Sources: PHP 2026 news archive; PHP advisory for CVE-2026-129289; PHP advisory for CVE-2026-115560; SecurityWeek.
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 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....
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...