PHP ships critical security fixes for every supported version: update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36
The PHP project released security updates on 19 November for all supported branches, fixing session, PHP-FPM and other flaws it rated up to Critical. Here is who is affected and what to do.
- Author
Umair Mateen- Published
- Reading time
- 4 min
- Category
- DevOps
Ideas in this post
Tap one for a 5-second answer. Underlined words in the article work the same way.
0 of 3 understood

The PHP project released security updates for every supported version on 19 November 2026: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. A day earlier it had warned that a critical security release was coming and that the highest severity among the fixes was Critical. PHP sits under WordPress, Drupal, Magento and many custom business apps, so if your website or internal tools run on PHP, this is one to schedule now, not at the next quarterly update.
PHP 8.6.0, the new major version, also shipped the same day. That is a feature release with its own migration work; you don't need to move to 8.6 to get the security fixes.
What was fixed
The official PHP 8 changelog lists 12 security advisories fixed in all four branches, with a few more that only affect newer versions (PHP 8.5.13 carries 18 security entries in total). The ones most worth knowing about:
Quick check · Everyday ↔ real
Match the kitchen to the real thing
Switch between the two and see how each part lines up.
- The diner placing an order
- The written order
- The kitchen room and stoves
- The cook reading the order
- The pantry
- The dish sent out
A kitchen that never closes
| Everyday | Real |
|---|---|
| The diner placing an order | Your browser (the client) |
| The written order | An HTTP request |
| The kitchen room and stoves | The server hardware |
| The cook reading the order | The server software |
| The pantry | The database |
| The dish sent out | The response, such as a web page |
From the explainer What is a server? Explained with a kitchen that never closes
- Sessions. Two flaws in how PHP stores and reads session data (the files that keep users logged in) can lead to remote code execution, meaning an attacker running their own code on your server. They are tracked as CVE-2026-126714 and CVE-2026-115560.
- PHP-FPM. FPM is the widely used process manager that runs PHP behind such as Nginx. The fixes cover request smuggling (an attacker sneaking a second request past your web server), a use-after-free bug that can lead to local privilege escalation, and a cross-site scripting issue on FPM's status page.
- CGI, Date, Phar, SOAP and core functions. Fixes include an out-of-bounds read and write in PHP-CGI, a timezone cache bug that can lead to remote code execution, a Phar signature bypass, SOAP memory and information-disclosure bugs, mixed-case HTTPS and FTPS addresses that could send data unencrypted, and a denial-of-service bug in handling headers.
There is useful context in the advance notice: the PHP team said its Critical-rated issues need either a non-default configuration or an uncommon setup to be exploited. That lowers the odds that a typical site is exposed, but you can't easily tell from the outside which settings your host or plugins use, so the safe answer is still to update.
Who should care
- Anyone running a PHP website or app, whether on a VPS, a dedicated server or a container image you build yourself. These are the cases where nobody else will patch it for you.
- Teams on managed hosting. Many hosts roll PHP updates automatically, but not all, and not always quickly. It is worth checking rather than assuming.
- Teams still on PHP 8.2. The PHP news archive notes that PHP 8.2 reaches end of life on 31 December 2026, after which it gets no more security fixes. Plan the move to 8.4 or 8.5 now.
- Anyone on PHP 8.1 or older. This release only covered the 8.2 to 8.5 branches, so older versions got no fix. They need an upgrade, not a patch.
Limits and caveats
The PHP announcements themselves give no CVSS scores or exploit details for each issue; the changelog lists the advisory and CVE IDs with one-line descriptions. Several security firms have published their own write-ups and names for the session bugs. Treat those as commentary and use the PHP changelog as the record of what was fixed and in which version.
If you run PHP from your Linux distribution's packages (Ubuntu, Debian, Red Hat and so on), the version number you see may differ: distributions often backport fixes into their own builds. Check your distribution's security notices for the matching package update.
What to do this week
- Find your PHP version. Run
php -von each server, or check your hosting control panel. Note every site and app, including . - Update to the fixed release for your branch: 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (or your distribution's patched package). Restart PHP-FPM afterwards so the new version is actually in use.
- Rebuild container images that bundle PHP, and redeploy them. An old image keeps the old PHP until it is rebuilt.
- Ask your host or agency to confirm in writing which version your site now runs, if you don't manage the server yourself.
- Lock down the FPM status page so it isn't reachable from the public internet, if you use it.
- Book the 8.2 upgrade before the end of the year if any of your sites still run it, and test plugins and themes against 8.4 or 8.5 first.
If you'd like a hand checking which of your apps run which PHP version and planning the upgrades, The DevDrift does this kind of maintenance work for small teams.
Sources
You’ve read the news. Now understand it.
- Learn · 5 min · Everyday ↔ realWhat is a server? Explained with a kitchen that never closesA server is a computer and its software that stay on, receive requests and send back pages, files or data. Explained with a kitchen that never closes: orders go in, dishes come out.Start in 5 seconds →
- Learn · 5 min · Everyday ↔ realWhat is an HTTP request? Explained with a letter and its replyAn HTTP request is the message your browser sends a server asking for something; the response is the reply, with a status code saying how it went. Explained with a letter to an order office and the stamped reply.Start in 5 seconds →
- Learn · 5 min · Put it in orderWhat is testing and staging? Explained with a trial dinner before opening nightTesting checks that new software works, and staging is a private copy of the live system where changes are tried before customers see them. Explained with a restaurant's trial dinner.Start in 5 seconds →


