# PHP Security Release 19 November 2026: Fixed Versions and How to Update

> PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix several critical flaws. Find the fixed version for your branch, check your setup, and update safely.

Source: https://www.epifive.com/blog/php-security-release-november-2026-update · Published 2026-11-19 · EpiFive

## Key takeaways

- PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 were released on 19 November 2026 and fix every vulnerability listed in this guide.
- GitHub rates at least seven php-src advisories from that day as Critical (CVSS v4 9.2 for the ones we opened), but each needs specific conditions.
- Run php -v and php-fpm -v separately, because the CLI and the web runtime can be different installs.
- Restart PHP-FPM or Apache after updating; installing the package alone does not replace running workers.
- PHP 8.2 reaches end of life on 31 December 2026, so plan a move to a newer branch.

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 were released on 19 November 2026 as security releases, and php.net tells every user of those branches to upgrade. If your server runs PHP 8.2.0 up to 8.2.35, 8.3.0 to 8.3.36, 8.4.0 to 8.4.27, or 8.5.0 to 8.5.12, you are on an affected version. Check the version, install the fixed release for your branch, restart PHP, and confirm.

This guide is defensive only. It names the affected components and conditions that the PHP project published, and it does not describe how to exploit them.

## Who this is for and what you will have at the end

This is for administrators and developers who run PHP on their own Linux or Windows servers, in Docker images, on a VPS, or on a hosting plan where they control the PHP version. By the end you will know which release to move to, whether your configuration matches the conditions in the critical advisories, what interim settings the PHP team documents, and how to prove the fixed version is the one serving web requests.

If you are on shared hosting with no shell access, your host controls the PHP binary. Ask the host which PHP build they run and whether they have rolled out these releases; use the version check later in this guide to see what your site reports.

## What was released

The php.net news page lists four security releases dated 19 November 2026, one per supported branch. It also lists a pre-announcement from 18 November: a release window of 14:00 to 14:30 UTC on 19 November, with the highest severity rated CRITICAL and issues that "need non-default or uncommon configurations."

| Branch | Fixed version | Affected range (per GitHub advisories) |
|---|---|---|
| PHP 8.5 | 8.5.13 | 8.5.0 to 8.5.12 |
| PHP 8.4 | 8.4.28 | 8.4.0 to 8.4.27 |
| PHP 8.3 | 8.3.37 | 8.3.0 to 8.3.36 |
| PHP 8.2 | 8.2.36 | 8.2.0 to 8.2.35 |

PHP 8.2 reaches end of life on 31 December 2026, as stated on php.net's news page. The 8.2.36 release is therefore one of the last you will get on that branch; start planning a move to 8.3 or newer.

Earlier fixes still matter. The previous security release on 21 October 2026 (8.5.12, 8.4.27, 8.3.36, 8.2.35) fixed two critical unauthenticated remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, and the new versions include those fixes. If you skipped October, going to the November version covers both.

## The critical advisories and the conditions each one needs

The php-src security advisories page showed ten advisories on its first page, all published on 19 November 2026: six Critical, one High and three Moderate. CVE-2026-115560 is rated Critical on its own advisory page, so there are at least seven Critical issues, and the listing spans several pages. The changelog entries for 8.5.13 and 8.4.28 map each one to a CVE. Below are the Critical ones, with the conditions the advisory text gives. Five rows were opened in full in this run; for the last two only the title and rating were read.

| Advisory | CVE | Component | Conditions stated in the advisory |
|---|---|---|---|
| Session serializer mismatch can lead to remote code execution | CVE-2026-115560 | Session | Session upload progress enabled; session data written with one serializer and read with another; a usable deserialization gadget chain in the reading application |
| Partially overwritten session files can lead to remote code execution | CVE-2026-126714 | Session | Default `files` session handler; attacker can influence session contents and interrupt a write; usable gadget chain |
| PHP-FPM request smuggling through an unread HTTP request body | CVE-2026-129289 | FPM | Front end that keeps backend connections persistent; application opens `php://input` without reading it fully |
| Timezone cache use-after-free can lead to remote code execution | CVE-2026-129496 | Date | Non-thread-safe build; startup diagnostic; PHP errors written through the file-based `error_log`; an early request diagnostic in a fresh worker |
| Use-after-free in magic method backtraces can lead to remote code execution | CVE-2026-129474 | Core | PHP 8.5 only; fatal error backtraces on with `zend.exception_ignore_args=0` |
| Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown | CVE-2026-129182 | Core | Conditions not read in this run |
| Use-after-free after interrupted session shutdown | CVE-2026-129481 | Session | Conditions not read in this run |

The advisories we opened score 9.2 on CVSS v4.0. Each carries an "Attack Requirements: Present" element in its vector, which matches the project's statement that the issues need special circumstances. That does not make them safe to ignore: several of the conditions are common defaults or common deployment choices, for example the `files` session handler is PHP's default and nginx with persistent FastCGI connections is a normal tuning step.

The rest of the changelog is also security-relevant. It lists a PHP-FPM epoll use-after-free that can lead to local privilege escalation (CVE-2026-129291, rated High), a PHP-FPM status page cross-site scripting fix (CVE-2026-129292), a PHAR OpenSSL signature bypass (CVE-2026-128090), SOAP fixes, and a fix for mixed-case HTTPS and FTPS URLs that could expose data in plaintext (CVE-2026-128064). One update covers all of them.

## Step 1: find out which PHP you are running

Many servers have more than one PHP. A server can run PHP 8.4 in PHP-FPM for the website while the command line points at a different version. Check each runtime separately.

```bash
# Command-line PHP
php -v

# PHP-FPM (binary name varies: php-fpm, php-fpm8.4, php8.4-fpm, php-fpm84)
php-fpm -v

# List installed PHP packages on Debian/Ubuntu
dpkg -l | grep -i '^ii.*php'

# List installed PHP packages on RHEL-family systems
rpm -qa | grep -i php
```

The first line of `php -v` begins with `PHP` followed by the version number. Compare it against the fixed version for the branch in the table above. A version lower than the fixed one on the same branch is affected.

To see what the web runtime reports, create a temporary file that prints the version, load it in a browser, and delete it straight away. Do not leave a `phpinfo()` page on a public server.

```php
<?php echo PHP_VERSION, ' ', PHP_SAPI, ' ', (PHP_ZTS ? 'ZTS' : 'NTS'), PHP_EOL;
```

The `PHP_ZTS` constant tells you whether the build is thread-safe. This matters for the timezone advisory, which applies to non-thread-safe builds.

### Docker

For images based on the official `php` image on Docker Hub, the tag decides the PHP version. Docker Hub's page describes the `cli`, `apache` and `fpm` variants and an `alpine` suffix, for example `php:8.2-fpm-alpine`. Pull the image again so you receive the rebuilt version, rebuild your own images from it, redeploy, and then run `php -v` inside the running container. We did not verify which exact tags Docker Hub had published at the time of writing, so check the tag list and confirm the container reports the fixed version.

## Step 2: update

### Linux distribution packages

Distributions often backport security fixes without changing the upstream version number. A package whose version looks old, with a distribution suffix, may already contain the fix, or may not. Use your distribution's own security tracker and changelog to confirm the specific CVE IDs above are fixed, rather than relying only on the version string. The generic commands are:

```bash
# Debian/Ubuntu
sudo apt update
sudo apt install --only-upgrade 'php*'

# RHEL-family
sudo dnf upgrade 'php*'
```

If you use a third-party repository for newer PHP builds, such as the Sury or Remi repositories, update from that repository and check its announcement for the fixed build. We did not open those repositories in this run.

### Building from source or using Windows

Source tarballs and Windows binaries are on the php.net downloads page, linked from each release announcement. The 8.5.13 announcement links the Windows page for the 8.5 branch. Replace the PHP folder as your deployment process requires, keep your `php.ini`, and compare the new `php.ini-production` for changed directives.

### Control panels and hosting platforms

cPanel, Plesk and similar panels ship PHP through their own channels. Check the panel's PHP version manager and its release notes. If the panel does not yet list a fixed build, apply the interim mitigations below where you can and watch for the panel's update.

## Step 3: restart so the new code is actually running

Installing a package does not replace PHP code already loaded in running worker processes. Restart the service that runs PHP:

```bash
# PHP-FPM (service name varies by distribution and version)
sudo systemctl restart php8.4-fpm

# Apache with mod_php
sudo systemctl restart apache2
```

A graceful reload is not a substitute when you need the new binary loaded. After the restart, confirm the FPM master process started recently:

```bash
ps -o pid,lstart,cmd -C php-fpm8.4
```

Adjust the process name to match your install.

## Step 4: verify

1. Run `php -v` and `php-fpm -v` and compare with the fixed version for your branch.
2. Load your temporary version page, or check the `X-Powered-By` header if your site exposes it, and confirm the web runtime reports the fixed version. Delete the temporary page afterwards.
3. In Docker or Kubernetes, run `php -v` in a running container from the new image, not just the build stage.
4. Confirm that each server behind a load balancer has the update, not only the one you tested.

## Interim mitigations from the advisories

Use these only until you can install the fixed release. Each one addresses a single advisory.

### Session upload progress (CVE-2026-115560 and CVE-2026-126714)

The fixed releases disable upload progress by default and reject runtime changes to session settings while it is enabled, according to the advisory. Until you update, set the following where the session store can be written, then restart PHP workers:

```text
session.upload_progress.enabled=0
```

If you must keep upload progress on, every reader and writer of a shared session store must use the same `session.serialize_handler`. The October advisory on this same setting recommended the same directive.

### PHP-FPM request smuggling (CVE-2026-129289)

The advisory lists these steps: disable backend connection reuse on the front end (for nginx the `fastcgi_keep_conn` directive, for Apache `mod_proxy_fcgi` the `enablereuse` option), read `php://input` fully on every request, and never expose PHP-FPM or LSAPI listeners to untrusted networks. It notes that reading the input alone is unreliable because error paths can leave data unread.

### Magic method backtraces on PHP 8.5 (CVE-2026-129474)

The advisory says the demonstrated remote attack needs `fatal_error_backtraces=1` together with `zend.exception_ignore_args=0`, and that `php.ini-production` sets `zend.exception_ignore_args=1`, which blocks that path. If you run PHP 8.5 with a development-style configuration, set it to `1` or turn `fatal_error_backtraces` off, and restart workers. Check the effective settings in the PHP-FPM pool as well as `php.ini`; the advisory says changing only the CLI configuration is not enough.

### Timezone cache (CVE-2026-129496)

The advisory's interim steps are to remove the configuration errors and deprecated settings that cause startup warnings, restart the master and all workers, and send PHP errors to a destination such as syslog instead of the file-based path. Check the PHP error log for startup warnings, for example an invalid `date.timezone` value.

## Troubleshooting

### php -v shows the old version after updating

The command line may be using a different binary. Run `which php` and `type -a php`, and check whether a version manager, a container, or another install appears earlier in `PATH`.

### The site still reports the old version

PHP-FPM or Apache was not restarted, or a different pool or container serves the site. Restart the correct service and check the web runtime, not the CLI.

### An update is not available from the distribution yet

Apply the interim mitigations above, limit who can reach PHP-FPM, and check the distribution tracker for the CVE IDs. Do not edit the version string or hold back unrelated updates.

### An application breaks after the update

The fixed releases change session behavior: upload progress is disabled by default and runtime changes to session settings are rejected while it is enabled, per the session advisory. If an application relied on upload progress or switched `session.serialize_handler` at runtime, re-enable the feature explicitly and make serializers consistent, or fix the application. Test in staging first.

## Checklist

- Identify every PHP runtime: CLI, FPM, Apache module, containers.
- Move to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or a distribution build that lists the CVE IDs as fixed.
- Restart PHP-FPM or Apache and confirm the web runtime version.
- Apply the interim mitigations if you cannot update today.
- Plan the exit from PHP 8.2 before 31 December 2026.

For a related example of a same-day server patch, see our guide to the NGINX HTTP/2 flaw at /blog/nginx-http2-cve-2026-123007-patch-guide, and for Java servers see /blog/java4shell-cve-2026-114938-openjdk-check-patch-workaround.

## What we checked

- Opened the php.net news page on 2026-11-19 and confirmed four security releases dated 19 Nov 2026: 8.5.13, 8.4.28, 8.3.37 and 8.2.36, plus the 18 Nov pre-announcement and the 31 December 2026 end-of-life note for PHP 8.2.
- Opened the php.net releases page on 2026-11-19; its listing for 8.2 to 8.5 still showed the October versions, so we relied on the news page and changelog for the new numbers.
- Read the 8.5.13 and 8.4.28 entries in the php.net ChangeLog and matched the GHSA IDs and CVE IDs to the table above. The 8.3.37 and 8.2.36 entries were not read; the advisories' affected and patched ranges cover them.
- Opened the GitHub php-src security advisories list and the advisories for CVE-2026-115560, CVE-2026-126714, CVE-2026-129289, CVE-2026-129496 and CVE-2026-129474; the affected ranges, 9.2 CVSS v4 scores and conditions come from those pages. The advisories for CVE-2026-129182 and CVE-2026-129481 were not opened.
- Cross-checked the CVE-2026-115560 mitigation against The Hacker News coverage, which describes the same `session.upload_progress.enabled=0` interim step.
- Checked the Docker Hub page for the PHP image: it describes the cli, apache, fpm and alpine variants but did not list current tags in the text we could read.
- Not tested on a live server, container or hosting panel; the commands are standard system commands and were not run against a PHP install. Distribution package status, Sury and Remi repository builds, and cPanel or Plesk availability were not verified.

Last tested: 2026-11-19

## References

- PHP news and release announcements: https://www.php.net/news.php
- PHP 8.5.13 release announcement: https://www.php.net/releases/8_5_13.php
- PHP ChangeLog for PHP 8: https://www.php.net/ChangeLog-8.php
- PHP downloads: https://www.php.net/downloads.php
- php-src security advisories: https://github.com/php/php-src/security/advisories
- GHSA-658j-r8rw-q6mx (session serializer mismatch): https://github.com/php/php-src/security/advisories/GHSA-658j-r8rw-q6mx
- GHSA-qc49-hpvq-g2w6 (PHP-FPM request smuggling): https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
- GHSA-gr4f-wgx5-jpfv (timezone cache): https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv
- GHSA-fm2m-fjf5-v3cp (session files): https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
- GHSA-8mjj-2r7p-4hg2 (magic method backtraces): https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2
- The Hacker News coverage: https://thehackernews.com/2026/11/php-warns-of-critical-security-flaws.html
- Docker Hub official PHP image: https://hub.docker.com/_/php

## Frequently asked questions

### Which PHP versions fix the 19 November 2026 vulnerabilities?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The GitHub advisories list every version from 8.2.0 up to, but not including, those releases as affected. PHP 8.2 reaches end of life on 31 December 2026, per php.net.

### Is my server vulnerable if I never changed any PHP settings?

Possibly not exploitable today, but you should still update. The advisories describe the critical issues as needing particular conditions, such as a persistent FastCGI front end, a non-thread-safe build with startup warnings, or a deserialization gadget in your application. Those conditions are easy to meet by accident, so the safe action is the update.

### Do I need to restart PHP after updating?

Yes. Restart PHP-FPM, or Apache if you use mod_php, so running workers load the new binaries. Then confirm with php -v for the command line and with a phpinfo page or php-fpm -v for the web runtime, because the CLI and the web server can use different PHP installs.

### Can I fix this with a setting instead of updating?

Only partly. The advisories give per-issue interim steps, such as session.upload_progress.enabled=0 or disabling FastCGI connection reuse, but each covers one flaw. Treat them as a stopgap until you can install the fixed release.

