On 19 November 2026 the PHP project shipped five releases on the same day. Four of them, PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, are each announced on php.net with the same line: "This is a security release." The fifth is PHP 8.6.0, the new major version.
A day earlier the PHP security team had pre-announced the releases under the heading "Upcoming Critical PHP Security Release". The two sentences that matter are these:
"The highest severity is CRITICAL. The issues rated CRITICAL require either non-default configuration or uncommon setups."
That second sentence is the useful one, and it is the one most summaries will leave out. The rating is critical, but PHP itself says the critical issues need a configuration most installs do not have. The right response is not panic. PHP's own advice is to "prepare to upgrade promptly", and while you do, it is worth working out whether you are one of the unusual setups.
This is the next cycle after the October release we covered in PHP2Shell: what to do before and after the 21 October PHP fix. The CVEs are different this time.
What was released
Every supported branch got a release, and each one fixes a different number of advisories. Counted from the per-version entries in PHP's 8.x changelog:
| Release | GitHub advisories (GHSA) | CVE IDs |
|---|---|---|
| PHP 8.6.0 | 17 | 18 |
| PHP 8.5.13 | 17 | 18 |
| PHP 8.4.28 | 14 | 14 |
| PHP 8.3.37 | 13 | 13 |
| PHP 8.2.36 | 12 | 12 |
So there is no single number for "the PHP release". If you are on 8.3, the list that applies to you is the 8.3.37 section of the changelog, not a total someone added up across branches. The older branches having fewer entries does not mean they are safer. The changelog lists what each release fixes, not why an issue is absent from a branch, and you should not read anything into the difference.
PHP 8.6.0 deserves a note of its own. php.net announces it as a major language release: "This release marks a major update to the PHP language," with Partial Function Application, default values for readonly properties, the new Io\Poll API, clamp(), a \Time\Duration class and a SortDirection enum. It is not worded as a security release, but its changelog entry carries the same advisory fixes as 8.5.13. If you were planning to move to 8.6 anyway, 8.6.0 includes them. If you were not, you do not need a major upgrade to get the fixes: the patch release on your current branch has them.
Which fixes to read first
Neither the announcements nor the changelog publish a severity for each issue. "The highest severity is CRITICAL" describes the set, so we have not attached a rating to any single advisory below. What the changelog does give is a one-line description of each, and some descriptions are more alarming than others.
Four are described as able to lead to remote code execution. In the 8.6.0 and 8.5.13 changelogs:
- GHSA-8mjj-2r7p-4hg2, "Use-after-free in magic method backtraces can lead to remote code execution" (CVE-2026-129474). This one appears only in the 8.6.0 and 8.5.13 entries.
- GHSA-gr4f-wgx5-jpfv, "Timezone cache use-after-free can lead to remote code execution" (CVE-2026-129496).
- GHSA-fm2m-fjf5-v3cp, "Partially overwritten session files can lead to remote code execution" (CVE-2026-126714).
- GHSA-658j-r8rw-q6mx, "Session serializer mismatch can lead to remote code execution" (CVE-2026-115560).
The 8.4.28, 8.3.37 and 8.2.36 entries carry the last three. Two of the four are in session handling, which is worth noting if you have changed the session save handler or serializer from their defaults. That is our observation, not a statement from PHP about which issues need the uncommon setups.
Others worth checking against your setup. All five releases also carry these:
- PHP-FPM request smuggling through an unread HTTP request body (CVE-2026-129289). Relevant if you run PHP-FPM behind a web server or proxy.
- PHP-FPM epoll use-after-free, which the changelog says "can lead to local privilege escalation" (CVE-2026-129291). That is local, not remote: an attacker needs to be running code on the machine already. It matters most where several users share one FPM installation.
- PHP-CGI out-of-bounds read and write during PATH_INFO correction (CVE-2026-129538). Relevant only if you run PHP as CGI.
- PHAR OpenSSL signature bypass via algorithm downgrade (CVE-2026-128090). Relevant if you rely on PHAR signatures to trust an archive.
- Mixed-case HTTPS and FTPS URLs can expose data in plaintext (CVE-2026-128064). A URL written as
HTTPS://rather thanhttps://is the kind of input to think about here.
php.net does not mention exploitation in the wild for any of these, and it does not mention public exploit code.
What to do
- Upgrade to the patch release on your branch: 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or 8.6.0 if you are moving to 8.6.
- Check what is actually running, not what you think is installed.
php -von the command line and the version your web server runs can differ. A quick page with<?php echo PHP_VERSION;(deleted afterwards) orphp-fpm -vtells you what serves requests. - If you use distribution packages, the upstream version number may not change. Distributions backport fixes into their own package versions, so read the package changelog for the CVE IDs above rather than comparing version strings. On Debian and Ubuntu:
apt-get changelog php8.3-fpm | grep CVE-2026-129289, with your own package name. - If you use the official Docker images, rebuild with
--pulland check the version inside the new image before you deploy it. A cached base layer is the easiest way to ship the old PHP under a new tag. - Restart PHP after upgrading. FPM and Apache with mod_php keep the old binary in memory until their processes are replaced.
While you wait for a fix to reach you, the narrow-trigger advice is the useful part: find out whether you run FPM, CGI or PHAR signature checks, and whether you have changed session handling from the defaults. Those are the features the descriptions above name.
What we did on DeployBase
On 20 November 2026 we rebuilt our PHP 8.3 and PHP 8.4 hosting images on the new releases, 8.3.37 and 8.4.28, and moved the running apps that use them onto the new builds one at a time. Our webmail at mail.deploybase.io, which runs PHP-FPM, now runs 8.2.36. After each switch we checked the PHP version inside the container and that the site returned its own page. No databases or site settings were touched.
Sources, read 20 November 2026: php.net release announcements for PHP 8.6.0, 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (19 November 2026) and the "Upcoming Critical PHP Security Release" notice (18 November 2026), at php.net; per-version advisory lists from the PHP 8 ChangeLog.