The PHP security update of November 2026 is PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, released on 19 November 2026, and it fixes the two flaws in the news that let an attacker run code without logging in: CVE-2026-129289 in PHP-FPM and CVE-2026-129538 in PHP-CGI. If your PHP version is lower than the fixed release for your branch, update PHP and restart PHP-FPM, php-cgi or Apache. That is the only full fix.
Most servers are not exposed to the worst case, because both flaws need a specific setup. This guide shows which setups are affected, how to check your version and SAPI in one minute, and how to update on Debian 13, Ubuntu, the sury.org packages and Docker. Every command was run on a Debian 13 test server on 20 November 2026. If you run PHP on one of our VPS or VDS servers in Amsterdam, Dublin or Prishtina, you have full root, so every step below works as written.
Quick fix for Debian 13: run
apt update && apt install --only-upgrade 'php8.4-*'as root, then check thatphp-fpm8.4 -vprintsPHP 8.4.28. Until you can update, PHP's own advice for the FPM flaw is to keep backend connection reuse switched off (nginxfastcgi_keep_connoff, Apacheenablereuseoff), and for the CGI flaw to setcgi.fix_pathinfo=0for php-cgi.
Key facts, checked 20 November 2026:
- PHP posted an advance notice on 18 November 2026 and released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026, each marked "a security release" (php.net advance notice, PHP 8.4.28 announcement).
- The PHP 8.5.13 ChangeLog lists 18 security fixes, from the engine to FPM, CGI, sessions, SOAP and Phar (php.net ChangeLog).
- CVE-2026-129289, PHP-FPM request smuggling, is rated critical, CVSS v4.0 9.2, and needs a front end that reuses FastCGI connections (GHSA-qc49-hpvq-g2w6).
- CVE-2026-129538, a PHP-CGI out-of-bounds read and write, is rated medium, CVSS v4.0 6.9, and affects only
php-cgiwithcgi.fix_pathinfo=1, the default. PHP-FPM and mod_php are not affected (GHSA-5j3f-64r7-f564). - Debian 13 has the fix in
php8.4 8.4.28-1~deb13u1(DSA-6641-1), and Debian 12 inphp8.2 8.2.36-1~deb12u1(DLA-4916-1) (Debian security tracker). - This is not PHP2Shell. That was CVE-2026-109618 and CVE-2026-109619, fixed on 21 October 2026. If you skipped October, this update covers both, because each release includes the earlier fixes.
The two flaws in plain words
CVE-2026-129289: PHP-FPM request smuggling
A web server like nginx talks to PHP-FPM over FastCGI. Some setups keep that connection open and send many requests through it. PHP's advisory explains that when an application opens php://input but does not read the whole request body, PHP failed to throw away the unread bytes before the next request on the same connection. PHP-FPM could then read those leftover bytes as a brand new request, one that nginx or Apache never checked. The advisory says an unauthenticated attacker can use this to run their own PHP code with the rights of the PHP worker, with a single request.
The condition that matters for you is connection reuse. PHP names nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI setups that keep backend connections, and LSAPI. PHP's advisory states that standard nginx and Apache configurations, which close the FastCGI connection after each request, are not affected by the demonstrated attack. The flawed code goes back to PHP 5.6.0.
CVE-2026-129538: PHP-CGI path handling
When php-cgi runs with cgi.fix_pathinfo=1, it tidies up the script path the web server sends it. If the server sends a script path and a PATH_INFO value that don't match in length, PHP could read and write memory outside the buffer. The advisory says one unauthenticated request can crash the process and may expose memory; code execution "has been claimed, but has not been confirmed". It needs unusual web server mappings, or a php-cgi FastCGI port that untrusted clients can reach.
The other critical fixes in the same release
PHP's advance notice said the critical issues "require either a non-default configuration or an uncommon setup". These are the ones rated critical (all CVSS v4.0 9.2) and what each needs, from the GitHub advisories:
| CVE | Area | What it needs |
|---|---|---|
| CVE-2026-129289 | PHP-FPM | Front end that reuses FastCGI connections |
| CVE-2026-126714 | Sessions (files handler, the default) | Attacker influence over session data, an interrupted write and a gadget chain in the application (GHSA-fm2m-fjf5-v3cp) |
| CVE-2026-115560 | Sessions | Upload progress on and two different session serializers on the same sessions (GHSA-658j-r8rw-q6mx) |
| CVE-2026-129496 | Date (timezone cache) | A startup warning written to a file-based PHP error_log in a non-thread-safe build (GHSA-gr4f-wgx5-jpfv) |
| CVE-2026-129474 | Engine, PHP 8.5 only | fatal_error_backtraces=1 and zend.exception_ignore_args=0 (GHSA-8mjj-2r7p-4hg2) |
One more is worth knowing: CVE-2026-129291 (high, 8.8) lets someone who can already run PHP code in an FPM worker gain the rights of the FPM master, which usually runs as root, when catch_workers_output is on (GHSA-jm4m-qfqx-967m). On shared servers with many clients, that one matters.
Affected versions: vulnerable below, fixed in
The ranges come from the GitHub advisories for CVE-2026-129289 and CVE-2026-129538. The same four fixed releases apply to every CVE in the table above, except CVE-2026-129474, which affects 8.5 only.
| Branch | Vulnerable below | Fixed in | Released |
|---|---|---|---|
| PHP 8.5 | 8.5.13 | 8.5.13 | 19 Nov 2026 |
| PHP 8.4 | 8.4.28 | 8.4.28 | 19 Nov 2026 |
| PHP 8.3 | 8.3.37 | 8.3.37 | 19 Nov 2026 |
| PHP 8.2 | 8.2.36 | 8.2.36 | 19 Nov 2026 |
| PHP 8.1 and older | all | no upstream release (end of life) | ask your distribution |
PHP 8.2 gets no security fixes after 31 December 2026, according to the php.net 8.2.35 announcement. Distribution packages often keep an older version number and backport the fix, so on Debian or Ubuntu compare the package version, not only the PHP version.
Check your PHP version and SAPI
You need two answers: which version runs, and which SAPI serves your sites (FPM, CGI or the Apache module). The command line php can be a different version from the one behind your website, so ask each binary. As root on Debian 13:
php -v
php-fpm8.4 -v
php-fpm8.4 -i | grep -E "^Server API|^Loaded Configuration"
On our patched test server:
PHP 8.4.28 (cli) (built: Nov 18 2026 10:55:31) (NTS)
...
PHP 8.4.28 (fpm-fcgi) (built: Nov 18 2026 10:55:31) (NTS)
...
Server API => FPM/FastCGI
Loaded Configuration File => /etc/php/8.4/fpm/php.ini
fpm-fcgi means PHP-FPM, cgi-fcgi means php-cgi, and cli is only the command line. Which packages are installed tells you the same thing:
dpkg -l "php8.4*" | grep ^ii
ii php8.4-cli 8.4.28-1~deb13u1 amd64 command-line interpreter for the PHP scripting language
ii php8.4-common 8.4.28-1~deb13u1 amd64 documentation, examples and common module for PHP
ii php8.4-fpm 8.4.28-1~deb13u1 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary)
ii php8.4-opcache 8.4.28-1~deb13u1 amd64 Zend OpCache module for PHP
ii php8.4-readline 8.4.28-1~deb13u1 amd64 readline module for PHP
A php8.4-cgi line means php-cgi is installed (check whether your web server uses it), and libapache2-mod-php8.4 means the Apache module. If you only have access to the website, put a file with <?php phpinfo(); in the web root, open it, read the "Server API" line and the version at the top, then delete the file straight away.
Are you in the risky setup?
For the FPM flaw, look for connection reuse in the web server config. On our test server with a stock nginx, grep found nothing (exit code 1), which is the safe default:
grep -rniE "fastcgi_keep_conn|enablereuse" /etc/nginx /etc/apache2 2>/dev/null; echo rc=$?
rc=1
Any line with fastcgi_keep_conn on or enablereuse=on means you are in the setup PHP describes, and patching comes first. For the CGI flaw, check the setting php-cgi uses:
php-cgi8.4 -i | grep cgi.fix_pathinfo
<tr><td class="e">cgi.fix_pathinfo</td><td class="v">On</td><td class="v">On</td></tr>
php-cgi prints its info as HTML, so you see table tags. On is Debian's default.
Update on Debian 13
Debian 13 ships PHP 8.4. The Debian tracker for php8.4 on 20 November 2026 lists trixie (security) as fixed in 8.4.28-1~deb13u1, while the plain trixie archive still holds the vulnerable 8.4.24-1~deb13u1, so you need the trixie-security line in your apt sources. We put our test server on 8.4.24 first and updated it:
apt update
apt list --upgradable
apt install --only-upgrade 'php8.4-*'
php8.4-cgi/stable-security 8.4.28-1~deb13u1 amd64 [upgradable from: 8.4.24-1~deb13u1]
php8.4-cli/stable-security 8.4.28-1~deb13u1 amd64 [upgradable from: 8.4.24-1~deb13u1]
php8.4-common/stable-security 8.4.28-1~deb13u1 amd64 [upgradable from: 8.4.24-1~deb13u1]
php8.4-fpm/stable-security 8.4.28-1~deb13u1 amd64 [upgradable from: 8.4.24-1~deb13u1]
...
Setting up php8.4-fpm (8.4.28-1~deb13u1) ...
Setting up php8.4-cgi (8.4.28-1~deb13u1) ...
The package changelog confirms which CVEs the Debian build covers:
zcat /usr/share/doc/php8.4-fpm/changelog.Debian.gz | head -12
php8.4 (8.4.28-1~deb13u1) trixie-security; urgency=high
* New upstream version 8.4.28
+ [CVE-2026-129538] PHP-CGI out-of-bounds read and write during
PATH_INFO correction.
+ [CVE-2026-129496] Timezone cache use-after-free can lead to remote
code execution.
+ [CVE-2026-129289] PHP-FPM request smuggling through an unread HTTP
request body.
...
If apt-cache policy php8.4-fpm shows no debian-security trixie-security line, fix your sources first. To get the next fix by itself, set up automatic updates as in our Debian 13 automatic security updates guide. Installing PHP from scratch is covered in how to install PHP on Debian 13. Debian 12 users get php8.2 8.2.36-1~deb12u1 through DLA-4916-1.
Update on Ubuntu
Ubuntu backports fixes into its own versions. For CVE-2026-129289, the Ubuntu CVE tracker on 20 November 2026 lists php8.3 on 24.04 LTS as fixed in 8.3.6-0ubuntu0.24.04.14, php8.5 on 26.04 LTS as fixed in 8.5.4-0ubuntu1.6, and php8.1 on 22.04 LTS as fixed in 8.1.2-1ubuntu2.29. So php -v on 24.04 still says 8.3.6 after the update; the package version is what proves the fix. Use the same apt commands as on Debian with your branch's package names (php8.3-* on 24.04, php8.5-* on 26.04) and compare with apt-cache policy. Check the other CVEs on the same tracker. For a fresh setup, see how to install PHP on Ubuntu.
Update PHP from sury.org (Ondrej Sury packages)
If you added packages.sury.org to get PHP 8.5 or several versions side by side, Debian's security archive does not update those packages. On 20 November 2026 the sury.org trixie repository carried 8.4.28-2+debsuryorg13.1+php+1 and 8.5.13-2+debsuryorg13.1+php+1. Run apt update and upgrade every branch you have installed, for example apt install --only-upgrade 'php8.5-*' 'php8.4-*', then check each php-fpmX.Y -v. Default unattended-upgrades settings skip this repository unless you add its origin.
Update PHP in Docker
The official php images on Docker Hub had tags for 8.5.13, 8.4.28, 8.3.37 and 8.2.36 by 20 November 2026 (Docker Hub php tags). Updating a running container does nothing: pull the new image, rebuild any image built FROM php:..., and recreate the container. If you pin a patch tag like php:8.4.27-fpm, change it to 8.4.28. Afterwards run php -v inside the new container to confirm.
Mitigations if you cannot update today
These are the vendor's own words, summed up. PHP says to upgrade; the steps below lower the risk but do not replace the fix.
- CVE-2026-129289: keep backend connection reuse disabled (nginx
fastcgi_keep_connoff, Apacheenablereuseoff) and never expose PHP-FPM or LSAPI listeners to untrusted networks. - CVE-2026-129538: set
cgi.fix_pathinfo=0for php-cgi and check that your routing still works, or correct the web server mapping; restrict direct access to FastCGI listeners. - CVE-2026-126714 and CVE-2026-115560: disable
session.upload_progress.enabledin server config if you don't need it, and limit untrusted data stored in sessions. - CVE-2026-129496: fix configuration errors and deprecated settings that cause startup warnings, or send PHP errors to syslog instead of a file, then restart the PHP master and all workers.
On our Debian 13 server, php-fpm8.4 -i reported session.upload_progress.enabled => Off and session.save_handler => files. Check your own value with the same command, because panels and images change it.
Verify after updating
The package restarts PHP-FPM, but confirm that the running service started after the new binary was installed:
systemctl restart php8.4-fpm
systemctl show php8.4-fpm -p ActiveEnterTimestamp
php-fpm8.4 -v | head -1
ActiveEnterTimestamp=Fri 2026-11-20 23:03:07 UTC
PHP 8.4.28 (fpm-fcgi) (built: Nov 18 2026 10:55:31) (NTS)
Restart Apache too if you use mod_php, and any process manager that runs php-cgi. For the final proof, load a page that prints PHP_VERSION through the web server, since that is the PHP visitors reach. If you also manage nginx, our nginx CVE-2026-123007 check and patch guide uses the same version-first method.
Frequently asked questions
What is the PHP security update of November 2026?
It is the release of PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026. php.net marks all four as security releases. They fix 18 security issues listed in the PHP ChangeLog, including CVE-2026-129289 in PHP-FPM and CVE-2026-129538 in PHP-CGI.
Is my server vulnerable to CVE-2026-129289?
Only if PHP-FPM sits behind a front end that reuses FastCGI connections, such as nginx with fastcgi_keep_conn on or Apache with enablereuse=on, and an application path opens php://input without reading it fully. PHP says standard nginx and Apache setups are not affected by the demonstrated attack. Update anyway, because other fixes in the same release apply to default setups.
Does CVE-2026-129538 affect PHP-FPM or mod_php?
No. PHP's advisory says PHP-FPM and PHP running as an Apache module are not affected. Only the php-cgi binary in CGI or FastCGI mode with cgi.fix_pathinfo=1 is, and only with particular web server mappings or an exposed FastCGI listener.
Which Debian package fixes these PHP flaws?
On Debian 13, php8.4 8.4.28-1~deb13u1 from trixie-security (DSA-6641-1). On Debian 12, php8.2 8.2.36-1~deb12u1 (DLA-4916-1). Check with apt-cache policy php8.4-fpm.
Why does Ubuntu still show PHP 8.3.6 after the update?
Ubuntu keeps the version number of each release and backports security fixes into it. On 24.04 LTS the fix for CVE-2026-129289 is package 8.3.6-0ubuntu0.24.04.14. Compare the full package version with the Ubuntu CVE tracker, not the short version from php -v.
Is this the same as PHP2Shell?
No. PHP2Shell was CVE-2026-109618 and CVE-2026-109619, fixed on 21 October 2026 in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The November releases are newer and contain those fixes as well.
What about PHP 8.1 and older?
PHP 8.1 and older get no upstream release. The GitHub advisory for CVE-2026-129291 lists 8.1.20 to 8.1.34 as affected with no patched version. Ask your distribution whether it backports fixes, or move to 8.4 or 8.5.
Need a hand?
The update itself takes a minute; finding every PHP install across old VMs, panels and containers is the slow part. If an old server runs an end-of-life PHP and you'd rather start clean, move the sites to a fresh Debian 13 VPS or VDS with NVMe in Amsterdam, Dublin or Prishtina with PHP 8.4.28 from day one and free weekly backups. For PHP sites that need guaranteed CPU under load, a VDS with dedicated vCPUs is the better fit. We also do custom offers, custom setups and systems built for you, such as a migration off an old PHP version, quoted per job: write to us on Telegram or at info@rscomputers-ks.com.