PHP Security Release Nov 2026: Fixes in 8.5.13 & 8.4.28
DEV Community

PHP Security Release Nov 2026: Fixes in 8.5.13 & 8.4.28

Last updated: 19 November 2026, the day of the release. The advisory details for individual CVEs were still being published when I wrote this. See How this was checked.

The PHP team warned on 18 November that its regular release on 19 November would carry fixes for "all supported PHP versions", with a highest severity of critical.

The releases are now out: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The release notes list 12 CVEs fixed on every supported branch, plus more on the newer ones.

This article sorts out what was fixed, what the one widely discussed bug (CVE-2026-115560) needs in order to be exploitable, how to check your own servers, and why checking the version number alone can mislead you.

The short version

  • Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or to a distribution package that lists the CVEs below as fixed.
  • PHP 8.1 and older are not in this release. They are no longer supported, so assume they will not get these fixes.
  • The flaw most discussed in advance, CVE-2026-115560, is a session-related remote code execution bug that needs an unusual setup. Check whether your code matches it (commands below) rather than guessing.
  • The release also fixes bugs in PHP-FPM, PHP-CGI, the timezone cache, PHAR, SOAP and the HTTP stream wrapper that do not depend on that setup.

How we got here

  • 21 October 2026: an emergency release (8.5.12, 8.4.27, 8.3.36, 8.2.35) fixed CVE-2026-109618 and CVE-2026-109619, together known as "PHP2Shell", which allow unauthenticated remote code execution through crafted HTTP requests. Press coverage reports limited active exploitation; I did not verify those reports independently.
  • 23 October: PHP published an informational advisory about CVE-2026-115560, described as a remote code execution vector in session upload progress, with the full advisory promised for the next regular release. It recommended disabling session upload progress as an interim measure.
  • 18 November: the php.net notice announced that the 19 November release (between 14:00 and 14:30 UTC) would address vulnerabilities affecting all supported versions.
  • 19 November: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 were released.

The October fixes do not fix CVE-2026-115560. Updating to 8.x.12, 8.x.27, 8.3.36 or 8.2.35 was not enough.

What was fixed

This list comes from the php-src release notes (the NEWS file) for the release tags. The wording below is the project's own. I compared the CVE lists for 8.4.28, 8.3.37 and 8.2.36 against the release announcement and they matched.

Fixed on every supported branch (8.5, 8.4, 8.3, 8.2):

  • CVE-2026-115560 Session Session serializer mismatch can lead to remote code execution
  • CVE-2026-126714 Session Partially overwritten session files can lead to remote code execution
  • CVE-2026-129496 Date Timezone cache use-after-free can lead to remote code execution
  • CVE-2026-129538 CGI PHP-CGI out-of-bounds read and write during PATH_INFO correction
  • CVE-2026-129289 PHP-FPM Request smuggling through an unread HTTP request body
  • CVE-2026-129292 PHP-FPM Status endpoint XSS via unescaped user and script fields
  • CVE-2026-129291 PHP-FPM epoll use-after-free can lead to local privilege escalation
  • CVE-2026-128090 PHAR OpenSSL signature bypass via algorithm downgrade
  • CVE-2026-129506 SOAP Use-after-free when processing DTD entity references
  • CVE-2026-15353 SOAP Information disclosure through malformed array dimensions
  • CVE-2026-128064 Streams Mixed-case HTTPS and FTPS URLs can expose data in plaintext
  • CVE-2026-127960 Streams Denial of service through folded HTTP response headers

Fixed on some branches only:

  • 8.5, 8.4 and 8.3: CVE-2026-129481, use-after-free after interrupted session shutdown.
  • 8.5 and 8.4: CVE-2026-129501, double free during DOM XML serialization.
  • 8.5 only: CVE-2026-129474 (use-after-free in magic method backtraces, can lead to remote code execution), CVE-2026-129182 (use-after-free via repopulation of last_fatal_error_backtrace after shutdown), CVE-2026-129438 (incorrect RFC 3986 URI serialization for oversized input) and CVE-2026-48841 (upgrade to uriparser 1.0.3).

On severity: PHP's notice says the highest severity is critical. None of the sources I read gave CVSS scores, and none said which individual CVE is the critical one. I am not going to guess.

The release notes label the session, timezone and (on 8.5) magic-method bugs as able to lead to remote code execution, so those are the ones to look at first.

CVE-2026-115560: who is actually exposed

The advisory material says an application is exposed only if both of these hold:

  1. Its configuration sets session.serialize_handler to php_binary or php_serialize, and its code switches the handler to php with ini_set() before calling session_start().
  2. Session upload progress is enabled. That is PHP's default.

The second condition is true on a stock install. On my test machine (PHP 8.3.6, Ubuntu package) session.upload_progress.enabled was On by default, and session.serialize_handler was php.

So it is the first condition, a mismatch between configured and runtime handlers, that separates exposed applications from the rest. The detailed mechanism was not in the sources I could read, so I will not explain it further.

Check your own code and config

Search for runtime changes to the handler. Remember that session_start() also accepts an options array, so search for the setting name rather than only for ini_set:

grep -rnE "serialize_handler" app src public --include=*.php

I tested that against three small files. It matched an ini_set('session.serialize_handler', 'php') call and a session_start(['serialize_handler' => 'php']) call, and did not match a plain session_start().

Then check the configured values on the server:

php -i | grep -E "^session\.(serialize_handler|upload_progress\.enabled)"
grep -rnE "^\s*(php_value|php_admin_value)?\s*\[?session\.(serialize_handler|upload_progress\.enabled)" /etc/php 2> /dev/null

The first command printed session.serialize_handler => php => php and session.upload_progress.enabled => On => On here. The second is a convenience search over config files and I only confirmed the pattern on a sample file; run php-fpm -i as well if you use FPM, since the FPM and CLI configurations can differ.

If you cannot patch today

The interim guidance was to turn session upload progress off. Two details from the sources and my test:

Set it in php.ini, an FPM pool or the server configuration, not at runtime. The setting has the "per directory" access level: ini_get_all() reported access level 2 for session.upload_progress.enabled (the value of PHP_INI_PERDIR) and 7 (changeable anywhere) for session.serialize_handler, and ini_set('session.upload_progress.enabled', '0') returned false. So an ini_set() call in your code will not turn it off.

Restart the PHP workers so the setting takes effect.

; php.ini or the FPM pool configuration
session.upload_progress.enabled = 0

That covers only this one CVE. It does nothing for the other eleven-plus fixes, so it is a stopgap, not a substitute for upgrading. Applications that never change the serialize handler at runtime are outside the described condition even with the default left on, but I would still patch.

Do Laravel apps need to care?

Partly. In the Laravel 13.40 framework source I have, there are no session_start() calls at all, because Laravel manages sessions through its own store rather than PHP's native session functions. So the session-specific bugs are less likely to apply to a plain Laravel app, but your own code or a package could still use native sessions, so run the grep above across vendor/ too if you are unsure.

The rest of the release (PHP-FPM, the timezone cache, SOAP, streams, PHAR) applies to a Laravel app the same as to any other.

Package versions can mislead you

Linux distributions usually backport fixes to their own PHP version instead of moving to the upstream one, so php -v may say 8.3.6 even on a patched machine. On the Ubuntu test box, php -v said 8.3.6, and the installed package was 8.3.6-0ubuntu0.24.04.13. Its changelog lists the October fix (CVE-2026-109618 and CVE-2026-109619) but none of this release's CVEs, at the time I checked it.

Compare CVE ids, not version numbers:

# Debian/Ubuntu: which CVEs does the installed package say it fixes?
zcat /usr/share/doc/php8.3-common/changelog.Debian.gz | grep -o "CVE-2026-[0-9]*" | sort -u

On RPM-based systems the equivalent is searching the package changelog, but I did not test that here. Distribution fixes usually trail the upstream release by some days.

Upgrade checklist

  • Inventory. List every place PHP runs: web servers, FPM pools, CLI cron hosts, queue workers, containers, CI images.
  • Pick the target. The newest patch release of the branch you are on (8.5.13, 8.4.28, 8.3.37 or 8.2.36), or a distribution package whose changelog lists the CVEs.
  • Test on staging with your real extension set and your test suite. I wrote up a way to run a Laravel app against several PHP versions in Test Your Laravel App on PHP 8.4 and 8.5 with Docker.
  • Rebuild container images from a fresh base so you pick up the new PHP. A running container keeps the PHP it was built with. I could not pull images from a registry in my environment, so I did not verify the availability of updated official images; check the registry yourself.
  • Restart long-running processes (FPM, queue workers, Octane or similar), because a new binary on disk does not change a process that is already running.
  • Verify afterwards: run php -v and, on distributions, the changelog check above, on every host.

If you are still on PHP 8.2: security fixes for 8.2 end on 31 December 2026 according to endoflife.date, so this release is among its last. Plan the move to a newer branch rather than staying put.

Related Dev Talk articles

  • Test Your Laravel App on PHP 8.4 and 8.5 with Docker
  • Laravel Security Checklist for Production

Frequently asked questions

Which PHP versions fix these vulnerabilities?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Older branches are not covered.

Is CVE-2026-115560 fixed in the October release?

No. The October releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) fixed the PHP2Shell CVEs, and CVE-2026-115560 was fixed on 19 November.

Is this being exploited?

Coverage reports limited exploitation of the October PHP2Shell bugs. I found no statement that the 19 November CVEs were being exploited, but that can change quickly after details are public.

Can I just disable session upload progress instead of upgrading?

It addresses one CVE only. Set it in php.ini or the FPM pool, not with ini_set(), and still upgrade for the rest.

My server says PHP 8.3.6. Is it unpatched?

Not necessarily. Distribution packages backport fixes without changing the upstream version number. Check the package changelog for the CVE ids.

update log

19 November 2026: first version, written on release day. To recheck: the full advisories and CVSS scores once published, the distribution fixes for Debian, Ubuntu and RHEL families, updated Docker image tags, and any reports of exploitation.

Sources

  • php-src NEWS for PHP 8.4.28
  • php-src NEWS for PHP 8.3.37
  • php-src NEWS for PHP 8.2.36
  • PHP release announcement for 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (PHP Foundation Discourse)
  • The Register: Get ready for another critical PHP security release to drop
  • The Hacker News: PHP warns of critical security flaws, fixes coming November 19
  • Aikido Security: PHP schedules a critical security release for 19 November
  • endoflife.date: PHP
  • Originally published on DEV Talk.
Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.