PHP Patches 18 Security Flaws, 7 Critical: What the November 2026 Release Means for Your Servers

PHP Patches 18 Security Flaws, 7 Critical: What the November 2026 Release Means for Your Servers

Patched for PHP2Shell in October? You still need this update. Here is what changed, who is most exposed, and how to check and patch PHP-FPM step by step.

If you patched your PHP servers for PHP2Shell last month and moved on, there is bad news: those servers are behind again. A new PHP release fixes 18 more security flaws, and seven of them are rated critical.

Today is November 20, 2026. PHP published the fixes on November 19 as part of its regular four-week release cycle, one day after the maintainers warned that critical bugs affected some less common setups. October's PHP2Shell flaws were exploited in real attacks, so attackers are already paying close attention to PHP. This post explains what was fixed, which servers are most at risk, and how to check and patch yours.

The versions you need

The fixed releases are:

Branch Safe from
PHP 8.5 8.5.13
PHP 8.4 8.4.28
PHP 8.3 8.3.37
PHP 8.2 8.2.36
PHP 8.6 8.6.0 (new release, includes the fixes)

The October versions (8.5.12, 8.4.27, 8.3.36 and 8.2.35) fixed PHP2Shell only. A server on one of those is still exposed to the November flaws. Not every flaw affects every branch, but the simple rule is to move to the versions above.

The headline flaw: a reused connection that skips your web server's checks

Most busy PHP sites are split into two parts. A front-end web server, such as nginx or Apache, receives requests and decides where each one may go. PHP-FPM (the FastCGI Process Manager) runs the PHP code behind it. To save time, some setups keep the connection between the two open and reuse it for many requests.

The flaw, CVE-2026-129289, rated 9.2, lives in that reused connection. If an application finishes a request without reading all of its body, the leftover bytes stay on the connection. PHP-FPM can then read them as a brand-new request, one the web server never checked or approved. According to PHP's advisory, an attacker who is not logged in can use this to run code with the permissions of the PHP worker.

Who is exposed, according to the security firm Aikido's analysis:

  • nginx or Apache set up to reuse FastCGI connections,
  • some HAProxy and LSAPI setups,
  • applications where a request can end with data left unread.

Standard nginx and Apache setups that close the backend connection after every request fall outside the demonstrated attack. Note that this is about the link between the web server and PHP, not about whether browsers keep their connection to your site open.

The other critical fixes

  • Session flaws (CVE-2026-115560, CVE-2026-126714): one involves the upload-progress feature, which records file upload progress in a user's session. Session data written in one format and read in another can be turned into an application object. This one had been public since October 23, and the October updates did not fix it. The other involves session files left half-written after an interrupted save. Whether either leads to code execution depends on the application's own code.
  • Leftovers from PHP2Shell (CVE-2026-129481, CVE-2026-129182): memory problems that the October fix for CVE-2026-109619 did not fully close. PHP 8.2 is not affected by the first one.
  • Engine memory bugs (CVE-2026-129474, CVE-2026-129496): one in the PHP 8.5 engine around errors inside "magic methods" (methods PHP calls automatically), one in the timezone cache at startup. The second one matters even for apps that barely use dates.

Seven critical ratings do not mean seven equally easy attacks. Several need specific settings or application code. That is a reason to plan the work sensibly, not a reason to skip it.

Two more fixes worth knowing

  • Secure addresses sent without encryption (CVE-2026-128064, rated 8.2): PHP's built-in HTTP and FTP handlers could accept an address like HTTPS:// written in mixed capitals but forget to turn on TLS, the encryption layer. Data such as tokens, cookies and passwords could then travel in plain text, including after a redirect.
  • Worker to master escalation (CVE-2026-129291): someone who already runs code inside a PHP-FPM worker could, on some Linux setups, gain the rights of the FPM master process. If the master runs as root, that means root.

Is anyone attacking this yet?

October's PHP2Shell flaws were used in real attacks. On November 12, Check Point Research reported attackers using them to break into about two dozen unpatched security gateways in one region. For the November flaws, the sources available on release day had not confirmed any attacks. Given how quickly PHP2Shell was picked up, it is wise not to wait.

How Rohit checks and patches Acme's servers

Rohit looks after a handful of PHP servers at Acme. Here is the order Rohit works in.

Step 1: Find the PHP version that actually serves traffic

php -v only shows the command-line PHP, which can differ from the one serving the website. Check the running FPM and the installed packages too:

php -v
ps -o args= -C php-fpm8.3 | head -1        # adjust to your FPM process name
php-fpm8.3 -v                              # the FPM binary's own version
dpkg -l | grep -E '^ii +php' | awk '{print $2, $3}'

On a server with several PHP installs, check each one. With Docker, run php -v inside each container.

Step 2: Check whether the web server reuses PHP-FPM connections

# nginx: look for connection reuse to PHP
grep -rnE 'fastcgi_keep_conn|keepalive' /etc/nginx/
# Apache with mod_proxy_fcgi: look for reuse on the PHP handler
grep -rni 'enablereuse' /etc/apache2/ /etc/httpd/ 2>/dev/null

If you see fastcgi_keep_conn on (used with an upstream block that has keepalive) or enablereuse=on, the server is in the group most at risk from CVE-2026-129289. Patch it first.

Step 3: Make sure PHP-FPM is not reachable from outside

PHP-FPM should listen on a Unix socket or on a local or trusted address only:

grep -rn '^listen' /etc/php/*/fpm/pool.d/
ss -ltnp | grep -E ':9000|php'

A listener like 0.0.0.0:9000 that the internet can reach needs fixing straight away.

Step 4: Patch, then restart PHP

Take a backup or snapshot first. Then update through your normal package source and restart PHP-FPM so the old workers go away:

sudo apt update
sudo apt install --only-upgrade 'php8.3*'
sudo systemctl restart php8.3-fpm

Distributions often fix bugs without changing the main version number, so also check the package changelog for the CVE numbers:

apt-get changelog php8.3-cli | grep -iE 'CVE-2026-(129289|115560|128064)'

For Docker, rebuild from a patched image tag and redeploy. For bundled stacks such as XAMPP, install a new stack release; system updates do not touch them.

Step 5: If you cannot patch today, reduce the risk

These are stopgaps, not fixes:

  • Turn off backend connection reuse between the web server and PHP-FPM, so every request gets a fresh connection.
  • Allow only trusted networks to reach PHP-FPM and LSAPI listeners.
  • For the upload-progress session flaw, set session.upload_progress.enabled = 0 in php.ini or the FPM pool, then restart the workers.

Step 6: Confirm the fix on the live site

Repeat Step 1 and confirm the running FPM shows the new version. Then load a few pages of each site to make sure everything still works. On servers patched in October, double-check the version number: an October version means the job is only half done.

Conclusion

The November 2026 PHP release is not a footnote to PHP2Shell. It fixes 18 more flaws, including a critical one that lets requests slip past the web server where PHP-FPM connections are reused. The safe versions are 8.5.13, 8.4.28, 8.3.37, 8.2.36 or 8.6.0. Check what version really serves your traffic, patch the servers that reuse FastCGI connections first, keep PHP-FPM away from the internet, and confirm the result on the live site.

Merits

  • Fixed versions are available for all supported branches on the same day.
  • The most serious flaw has a clear stopgap: turning off backend connection reuse.
  • Standard nginx and Apache setups fall outside the demonstrated attack for the top flaw.
  • Patched packages exist for older branches from third-party maintainers.
  • The checks in this post use standard tools already on most Linux servers.

Demerits

  • Servers patched in October need a second round of updates within a month.
  • Restarting PHP-FPM causes a short interruption on busy sites.
  • Bundled stacks and old Docker images are not fixed by system updates.
  • Distribution version numbers can hide whether a fix is included, so changelogs must be read.
  • PHP 8.2 reaches end of life on December 31, 2026, so those sites face another upgrade soon.

Caution

This article is educational. Acme, the example person Rohit, the PHP version in the commands, the process and service names and the file paths are placeholders; adjust them to your own servers and test changes on a non-production system first. The CVE numbers, ratings and fixed versions summarise PHP's announcement and security reporting as published at the time of writing. Check the official PHP advisories and your distribution's notices before relying on them, and only check systems you own or are authorised to manage.

Frequently asked questions

  • Which PHP versions fix the November 2026 vulnerabilities? — PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and the new PHP 8.6.0 includes the fixes.
  • I patched PHP2Shell in October. Am I safe? — No, the October versions fixed PHP2Shell only, so you still need the November release.
  • What is CVE-2026-129289? — A critical PHP-FPM flaw where leftover request data on a reused web server connection is treated as a new request, which can allow code execution without logging in.
  • How do I know if my server reuses PHP-FPM connections? — Look for fastcgi_keep_conn on with upstream keepalive in nginx, or enablereuse=on in Apache's FastCGI proxy settings.
  • Can I protect my server before patching? — Yes, turn off backend connection reuse, restrict PHP-FPM to trusted networks and disable upload-progress tracking, but treat these as temporary steps.
  • Are the November PHP flaws being exploited? — No attacks on the November flaws had been confirmed at release, but October's PHP2Shell flaws were exploited, so patch promptly.
  • Why does php -v not show the right version? — It shows the command-line PHP, while the website may run a different PHP-FPM binary, package or container.
  • What if I run an older PHP like 7.4 or 8.1? — Those branches get no official fixes; use a trusted maintainer's patched packages or upgrade to a supported branch.

Tags

#php #phpfpm #cybersecurity #patchmanagement #vulnerability #nginx #apache #linuxadmin #websecurity #devsecops

Free field guide

Docker Security Checklist

Lock down your containers from build to runtime — 29 practical controls covering images, runtime flags, secrets, and the daemon. Enter your email — you'll get the PDF instantly, plus new posts on Docker, Linux & security.