Skip to main content

PHP’s Scheduled Security Release Fixes Up to 18 Flaws in Every Supported Version, Several Labelled Remote Code Execution

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 shipped on 19 November. The project says its critical issues need unusual setups, which makes checking your configuration the first job.

Software developer coding on dual monitors in a well-lit modern office, focused and engaged.
KBY News Desk8 min read

In this article

Share

The PHP project shipped security releases on Thursday 19 November 2026 for every branch it still supports: 8.5.13, 8.4.28, 8.3.37 and 8.2.36, with the first stable 8.6.0 carrying the same fixes. Counting the CVE identifiers in each version’s ChangeLog entry, we make it 18 fixes in 8.5.13, 14 in 8.4.28, 13 in 8.3.37 and 12 in 8.2.36. Several are described in the project’s own ChangeLog as leading to remote code execution, in the session handling and timezone code.

The advance notice the project posted on Wednesday 18 November set the tone. It said the highest severity in the releases is critical, but that the issues rated critical need a non-default configuration or an uncommon setup. Our reading is that this is a patch-this-week release for most servers, not a patch-tonight one, with two exceptions covered below.

#Version by version, what the ChangeLog lists

The counts differ because some bugs only exist in newer code. These come from php.net’s own ChangeLog for each release, and we counted the CVE numbers ourselves.

ReleaseCVE identifiers listedLabelled remote code execution
PHP 8.5.13184
PHP 8.4.28143
PHP 8.3.37133
PHP 8.2.36123

The fixes that appear in all four branches are the ones to focus on, because they affect whatever supported version you run. The ChangeLog entries are brief, so what follows is only what the project’s own wording says, not what we have worked out about how they behave.

Two session bugs are described as leading to remote code execution: partially overwritten session files (CVE-2026-126714) and a session serializer mismatch (CVE-2026-115560). A third remote code execution entry is a timezone cache use-after-free (CVE-2026-129496). Beyond those, the shared list includes an out-of-bounds read and write in PHP-CGI’s PATH_INFO handling (CVE-2026-129538), request smuggling in PHP-FPM through an unread HTTP request body (CVE-2026-129289), a PHP-FPM epoll use-after-free that can lead to local privilege escalation (CVE-2026-129291), a cross-site scripting hole in the PHP-FPM status endpoint (CVE-2026-129292), a PHAR OpenSSL signature bypass through algorithm downgrade (CVE-2026-128090), two SOAP bugs (CVE-2026-15353 and CVE-2026-129506), mixed-case HTTPS and FTPS URLs that can expose data in plaintext (CVE-2026-128064), and a denial of service through folded HTTP response headers (CVE-2026-127960).

PHP 8.5.13 adds a fourth remote code execution entry, a use-after-free in magic method backtraces (CVE-2026-129474), and several more that the older branches do not list. The 8.6.0 ChangeLog carries the same fixes as 8.5.13.

#The bug that was once only a footnote

One identifier in that list has history. The Register reported on 18 November that CVE-2026-115560 was reserved in October for a remote code execution bug the PHP Foundation chose not to fix in an emergency release. At the time, executive director Elizabeth Barron told the outlet it needed “a very unlikely combination of configuration and specific PHP application code”, and the project published only an informational advisory telling users to set session.upload_progress.enabled=0 until the next regular release. That regular release is this one, and the fix for the session serializer mismatch is now in every supported branch.

That matters for how you read the severity. The project did not misjudge it in October: a bug that needs an unusual setup is a smaller risk than one any request can trigger. But “unusual” is a property of your applications, and you only know whether yours qualify if you check. The Register’s summary of that earlier advisory says the conditions involve an application setting session.serialize_handler to php_binary or php_serialize and then switching it to php at runtime. A code base that does that, or a framework it depends on that does, is where we would look first.

#Why October raises the stakes for this one

The previous emergency release, the PHP2Shell pair (CVE-2026-109618 and CVE-2026-109619), was far worse: the project’s advisory said all installations serving web requests were at risk and called the risk highest for mod_php. The Register reports that CISA added both to its Known Exploited Vulnerabilities catalogue on 26 October, and that researchers at Dream said suspected Chinese attackers chained them with a Linux kernel privilege escalation to compromise 25 servers as early as 23 October. We have not verified Dream’s research and attribute it to the Register’s account.

None of the sources we read reports exploitation of the November flaws, and the project says critical issues need non-default setups. But the project publishes the GHSA identifiers and short descriptions with the release, and we have written before about Google’s warning that attackers now use AI agents to turn patches into exploits. We expect the gap between a fix and a working exploit to keep shrinking, so the sensible assumption is that the details are now public enough to be studied. That is the reason to treat the unusual-configuration caveat as a reason to check, not a reason to wait.

#What to do before the weekend

These are our suggested steps, in the order we would take them.

  1. Find every PHP version you run. On a server, php -v and php-fpm -v report the command-line and FPM versions, and they can differ. Look inside containers too: the version in an old image tag does not change when the host is patched.
  2. Compare each against the fixed versions: 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Anything on a lower patch level of the same branch is affected by the fixes it lacks. On a Linux distribution, the version string may not move even when the fix is applied, because vendors backport patches. The PHP project said so in its October advisory, so read the vendor’s changelog for the CVE numbers above rather than trusting the version alone.
  3. Update through your normal channel, then restart PHP-FPM or Apache so running workers load the new code. An update on disk does not change a process that is still running.
  4. If you run PHP 8.1 or older, the project said in October that it no longer receives updates from the project, and that some distributions and long-term-support vendors provide backported fixes. Ask your vendor about this release specifically, or plan the move to a supported branch.
  5. Check whether the PHP-FPM status page is reachable from places it should not be. It is a diagnostic endpoint, and one of the fixes is for script injection in its output, so we would restrict it to localhost or a management network whatever your patch state.
  6. Look for applications that set session.serialize_handler at runtime or use a custom session handler, and note them for the application owner. This is the part that decides whether the session fixes were a theoretical risk for you or a real one.

For teams running nginx in front of PHP-FPM, this lands in the same week as F5’s fixes for two NGINX HTTP/2 flaws. It is worth patching the web server and the PHP layer in one maintenance window rather than two.

#If you have a website but no server

A good share of small organisations run a PHP site, often WordPress, on shared or managed hosting, and nobody there sees a command line. The host decides when the PHP version is updated, and you may be able to choose the branch in the hosting control panel. In WordPress, go to Tools, then Site Health, then the Info tab and open its Server section, which is where WordPress describes the server it runs on; the PHP version is normally listed there.

The one thing to do is ask the host a plain question: has the 19 November PHP security release been applied, and for which branch? If your site runs on an older branch that the host no longer updates, that is the larger problem, and a host that cannot say which version you are on is telling you something. Do not read a “no known issues” reply as a statement that the site is secure; it only says the host has not reported a problem.

#Where we land

This is a bigger release than its tone suggests. Eighteen fixes in the newest branch, remote code execution labels in all four, and a footnote bug from October finally closed. But the project’s own wording is careful: the worst issues need unusual setups, and we have seen no report of exploitation. Our view is that most teams should patch within days and use the unusual-configuration caveat to prioritise, not to postpone. We would change that if CISA lists any of these CVEs or a vendor reports attacks, and we will update this story if that happens.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01PHP.net: PHP 8.5.13 release announcementphp.net
  2. 02PHP.net: PHP 8 ChangeLog (8.6.0, 8.5.13, 8.4.28, 8.3.37 and 8.2.36)php.net
  3. 03PHP.net: 2026 news archive, including the 18 November advance notice and the October advisoryphp.net
  4. 04WordPress.org: Site Health screenwordpress.org
  5. 05The Register: Get ready for another critical PHP security release to droptheregister.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on PHP’s Scheduled Security Release Fixes Up to 18 Flaws in Every Supported Version, Several Labelled Remote Code Execution. Comments are checked for spam and held for moderation before appearing.

Loading comments...

More news

All news

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.