Skip to content

PHP’s 19 November security release: 18 vulnerabilities, seven of them critical

Section 1 of 8
Size 3 of 5

Security06/08

PHP’s 19 November security release: 18 vulnerabilities, seven of them critical

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix 18 flaws, seven critical: what each needs, how to update and verify, stopgaps, and what changes after the update.

Abdulwahed MohammadContent writer at tech+16 min read

On the evening of Thursday 19 November 2026, a few minutes after 14:00 UTC, the PHP team published four security releases at once: 8.5.13, 8.4.28, 8.3.37 and 8.2.36, together with 17 advisories on GitHub and an upgrade of the uriparser library. That makes 18 vulnerabilities: seven critical at 9.2 on the CVSS 4.0 scale, four high, six medium, and the library upgrade. It is PHP’s third security announcement in a month, after the PHP2Shell flaws on 21 October, and three of today’s fixes close paths left open after that round. The good news is that none of the critical flaws hits a server on its default configuration alone. By the evening of the release we had found no report of any of them being exploited, but the full details are now public, and in October only hours separated the announcement from exploitation. In this article: what each branch fixes, the condition each critical flaw needs so you can tell whether your server is concerned, how to update and verify, what to do if you cannot update today, and what changes in PHP’s behaviour after the update.

01What each branch fixes

Not every branch carries every fix, because some of the flaws are in code added in newer branches, such as the fatal error backtraces that came with PHP 8.5:

BranchPatched releaseFlaws fixedCritical
8.58.5.13187
8.48.4.28145
8.38.3.37135
8.28.2.36124; the branch’s support ends on 31 December 2026
8.1 and olderNo official releaseNothing from PHP itselfA fix from your distribution or an extended-support provider, if one comes

Some of these flaws are old: request smuggling through PHP-FPM goes back to PHP 5.6, and the Phar signature bypass to 5.3, so end-of-life branches are most likely exposed too. And a fix does not always carry the new version number: distributions, CloudLinux and extended-support providers backport fixes into their packages and sometimes keep the version, so for them the package changelog is what counts. CloudLinux began publishing patched packages about an hour after the release, and within two hours its stable repository held alt-php85, alt-php84 and ea-php 8.2 through 8.5, along with a patched ea-php81 that still reads 8.1.35; the remaining alt-php branches and the extended-support packages follow. cPanel shipped the four branches in EasyApache the same day.

02The seven critical flaws and what each needs

Every one of the seven critical flaws can end, if exploited, in code running on the server with the PHP worker’s privileges, that is . But the CVSS rating itself records attack requirements for each. So read those requirements as questions about your server:

Request smuggling through PHP-FPM (CVE-2026-129289)

This is the closest to practical exploitation, because it needs no memory corruption, no knowledge of addresses and no race. When an application opens a php://input stream and does not read it to the end, PHP treated the request body as consumed and left the rest of it on the connection. If the web server keeps the connection open between requests, PHP-FPM read that leftover as a new request that the web server never created or checked. That is : the smuggled request chooses the script that runs, the client address the application sees, and administrator settings themselves. It sets allow_url_include to 1 and auto_prepend_file to php://input, so its own body runs as PHP code, and the changed settings stay in force for later requests on the same worker.

The condition: a persistent connection between the web server and PHP-FPM, which is not the default. nginx has one with fastcgi_keep_conn on, Apache with enablereuse=on in mod_proxy_fcgi, and HAProxy when it keeps FastCGI connections; add an application path that opens php://input before reading it. The usual setup that closes the connection after each request does not carry the demonstrated attack. LiteSpeed’s LSAPI shares the underlying flaw, which desynchronises the requests on the connection, but the advisory does not establish code execution through it.

Three flaws in sessions

Three of the critical flaws are in the session extension, and the first two end in a from the application’s own classes: the attacker makes PHP rebuild objects from data they crafted, and those objects call functions while being built or destroyed that lead to command execution.

  • A session file that is half old (CVE-2026-126714): The files session handler, the default, wrote a new session over the old one without emptying the file first. If the write stopped halfway, the file held the start of the new session and the end of the old one, and could be read back as objects the attacker crafted. The condition: attacker data stored in the session, an interrupted write at a useful moment, and a usable gadget chain in the application.
  • Two formats for one session (CVE-2026-115560): The PHP team announced this one on 23 October without a fix; today it has one. Upload progress writes into the session in one format, and another application or process may read it in the php format, turning part of a key name into an object. The condition: upload progress enabled, a writer using php_binary or php_serialize and a reader using php on the same session directory. Separate FPM pools do not separate session storage on their own.
  • A session that never finished closing (CVE-2026-129481): In 8.3 and later, an incomplete fix for CVE-2026-109619 from the October round. A fatal error in a function called while the session closes, such as stream_close in an application’s stream wrapper, leaves a pointer to freed memory, which the next request on the same worker reaches, even one from another visitor. The report demonstrated memory corruption and worker crashes; code execution through this path has not been demonstrated yet.

The timezone cache after it is freed (CVE-2026-129496)

In every branch. If PHP writes a warning or deprecation notice to its error log file during startup, it allocates the timezone cache in temporary memory that is released after startup while its reference stays. If the first request to reach a fresh worker raises an early diagnostic, such as the max_input_vars warning, it reads that freed memory, which may hold data from the attacker’s request. This is a , and it was turned into command execution in the lab on PHP-FPM and mod_php, with known memory addresses and extra settings. The condition: a startup diagnostic, such as a wrong timezone in php.ini or a deprecated session setting, and PHP errors logged to a file rather than syslog. PHP-FPM’s own error log alone does not meet it.

PHP 8.5 only: fatal error backtraces

PHP 8.5 added backtraces for fatal errors, the fatal_error_backtraces setting, on by default, and it holds two flaws:

  • Arguments from freed memory (CVE-2026-129474): When a fatal error, such as exceeding memory_limit, strikes just as a magic method like __call or __callStatic is entered, the backtrace collects arguments left by an earlier call that may point to freed memory. Common interfaces such as Laravel’s facades go through these methods, although exploitation of a complete Laravel application has not been demonstrated. The condition: fatal_error_backtraces at 1 and zend.exception_ignore_args at 0. The php.ini-production file sets the latter to 1, which closes this path.
  • A backtrace that comes back after cleanup (CVE-2026-129182): October’s fix clears the backtrace at the end of a request, but a fatal error while modified settings are restored afterwards recreates it, and the next request reads it. The condition: per-path settings an administrator sets, such as max_memory_limit in both the global and a per-path configuration, or zlib.output_compression clashing with output_handler, plus an early diagnostic in the next request.

03The other flaws in the release

The remaining eleven are narrower, but the first deserves special attention on any server that runs code for more than one party:

  • From an FPM worker to root (CVE-2026-129291, high): When catch_workers_output is on, anyone who runs PHP code in an ordinary FPM worker can exploit freed memory in the PHP-FPM master process, which usually runs as root. On a shared server every site runs PHP code, so the flaw is a path from one account to the whole server.
  • HTTPS with a capital letter (CVE-2026-128064, high): file_get_contents, fopen and similar functions sent data unencrypted when the S of the scheme was a capital, as in HTTPS or httpS, and the same for FTPS, even when the address came from a redirect. Passwords and API tokens could leave in clear text for anyone watching the network.
  • Folded headers that burn the CPU (CVE-2026-127960, high): A malicious server answers a request PHP sends with a header split over thousands of lines, keeping the worker busy joining them. The attacker needs your application to fetch an address they own, or control of a server it already contacts.
  • A Phar signature downgraded to a hash (CVE-2026-128090, high): An OpenSSL-signed Phar archive can have its signature type switched to a SHA-256 hash anyone can compute, so PHP accepts modified contents without reading the public key. It concerns applications that download and run signed Phar archives.
  • php-cgi and PATH_INFO (CVE-2026-129538, medium): Out-of-bounds reads and writes in php-cgi when cgi.fix_pathinfo is 1, the default. PHP-FPM and mod_php are not affected.
  • The rest are medium: Two flaws in the SOAP extension that concern exposed SOAP endpoints, a double free in the modern DOM API when it serialises an untrusted document to XML in 8.4 and 8.5, script injection in the full PHP-FPM status page that runs in the browser of whoever opens it, a flaw in the new URI API in 8.5 with inputs close to 2 GB, and the upgrade of the uriparser library that API relies on.

04Check your server and update it

Start with what actually serves your site, not what the command line shows: php -v reads the CLI build, and the site may run another version through PHP-FPM, LiteSpeed or PHP Selector. Then look for the CVE numbers in the package changelog:

The version actually running and its SAPI, then the CVE numbers in the package changelogs
# The version and SAPI as your site sees them, not the command line (delete the file right after)echo '<?php echo PHP_VERSION, " ", PHP_SAPI, " upload_progress=", ini_get("session.upload_progress.enabled");' | sudo tee /var/www/html/ver-7d2.php >/dev/nullcurl -s https://dukkan-jbeil.com/ver-7d2.php; echosudo rm /var/www/html/ver-7d2.php# Debian and Ubuntu: does the package carry the fix? Change 8.3 to your branchapt changelog php8.3-fpm 2>/dev/null | grep -E 'CVE-2026-(129289|129496|126714)'# RHEL, AlmaLinux and CloudLinux: the system package, then alt-php and ea-php for each branch you userpm -q --changelog php-cli | grep -E 'CVE-2026-(129289|129496|126714)'rpm -q --changelog alt-php83-common | grep -E 'CVE-2026-(129289|129496|126714)'rpm -q --changelog ea-php83-php-common | grep -E 'CVE-2026-(129289|129496|126714)'

If the fix is missing, update, then restart everything that runs PHP. Old workers stay in memory with the affected code until they are restarted, and three of today’s critical flaws live in the worker itself from one request to the next.

Update, then restart everything that runs PHP
# Debian and Ubuntu: update, then restart everything that runs PHP (adjust the names to your server)sudo apt update && sudo apt upgradesudo systemctl restart php8.3-fpm nginx# RHEL and AlmaLinuxsudo dnf upgrade 'php*'sudo systemctl restart php-fpm httpd# cPanel with CloudLinux: the EasyApache and alt-php packages, then the web server and PHP-FPMsudo dnf clean all && sudo dnf upgrade 'ea-php*' 'alt-php*'sudo /scripts/restartsrv_httpd && sudo /scripts/restartsrv_apache_php_fpm# LiteSpeed: restart the server, then the detached lsphp processes that outlive itsudo /usr/local/lsws/bin/lswsctrl restartsudo touch /usr/local/lsws/admin/tmp/.lsphp_restart.txt# Docker: rebuild pulling the patched base image; a restart is not enoughdocker compose build --pull && docker compose up -d
ProblemAfter the update my app’s upload progress bar stopped working
FixThe fix made session.upload_progress.enabled off by default. If you need it, turn it on explicitly in php.ini or in the FPM pool, and keep everything that reads the same sessions on one session.serialize_handler.
ProblemChanging a session setting with ini_set now fails
FixWhile upload progress is on, PHP now refuses to change session settings during a request, session.serialize_handler included. Put the value in the configuration before the request starts, or turn upload progress off.
ProblemStartup lines in the PHP error log are now in UTC
FixThat comes from the fix itself: outside a fully initialised request, PHP writes log timestamps in UTC rather than the configured timezone.
Problemphp -v shows the new release but the web check shows the old one
FixThe old workers are still in memory. Restart PHP-FPM or the web server, and on LiteSpeed restart the detached lsphp processes as well.

05If you cannot update today

The PHP team published a temporary measure with each advisory; all of them buy time and none replaces the update:

  • A fresh FastCGI connection for each request: Remove fastcgi_keep_conn on from nginx, and the enablereuse=on option from mod_proxy_fcgi in Apache. That closes the demonstrated request-smuggling attack.
  • Turn off upload progress: Set session.upload_progress.enabled to 0 in administrator configuration: php.ini, or php_admin_value in the FPM pool, then restart the workers. That closes the path to CVE-2026-115560 and one path to CVE-2026-126714, and does nothing for CVE-2026-129481.
  • On PHP 8.5: Set zend.exception_ignore_args to 1 or fatal_error_backtraces to 0, in the configuration the workers read rather than the CLI one. The first closes the path to CVE-2026-129474; the second closes it and CVE-2026-129182 too.
  • Silence startup diagnostics: Fix every warning PHP writes at startup, such as a wrong timezone or a deprecated setting, then restart the master process and the workers, or send PHP’s error log to syslog instead of a file. That removes the condition CVE-2026-129496 needs.
  • Stop capturing worker output: Set catch_workers_output to no in every FPM pool, which closes CVE-2026-129291’s path from the worker to the master process.
  • And if you run php-cgi: Set cgi.fix_pathinfo to 0, then check that your application’s routes still work.
Temporary measures in the PHP-FPM pool and in nginx until you update
# /etc/php/8.3/fpm/pool.d/www.conf: temporary measures until you update, not a substitute for itphp_admin_value[session.upload_progress.enabled] = 0catch_workers_output = no# PHP error log to syslog instead of a filephp_admin_value[error_log] = syslog# PHP 8.5 onlyphp_admin_value[zend.exception_ignore_args] = 1php_admin_value[fatal_error_backtraces] = 0# nginx: a fresh FastCGI connection for each request (or delete the line)fastcgi_keep_conn off;# Then restart the master process and the workers, and read the effective values over the web as abovesudo systemctl restart php8.3-fpm nginx

06What changes after the update

Some of the fixes change how PHP itself behaves, so know them before your developers ask:

  • Upload progress is off by default: If you turn it on explicitly in any application or pool, keep everything that writes and reads the same sessions on one session.serialize_handler, because the fix does not enforce that across separate configurations. And an old explicit setting of 1 overrides the new default.
  • Session settings are fixed during a request: While upload progress is on, changing session settings at runtime is refused.
  • The session file is emptied before writing: An interrupted write may lose session data, but it no longer mixes with an old session.
  • PHP-FPM closes a suspicious connection: If a FastCGI input record is left incomplete, PHP-FPM closes the connection instead of accepting a new request on it.
  • A worker that stumbles during cleanup ends: If a fatal error cuts off an extension’s cleanup at the end of a request, PHP ends the process instead of serving another request with half-cleaned state.
  • Phar rejects a hash next to a key: If a public key file sits next to the archive, only an OpenSSL signature is accepted for it.

07How we handled it at Illevante

Illevante’s cPanel hosting servers run CloudLinux, the LiteSpeed web server and Imunify360, and each customer picks their site’s PHP version from 5.6 to 8.5 through PHP Selector. So our servers carry all four supported branches, and branches PHP itself no longer releases anything for. This is how we followed this release:

  1. 01Advance notice: We announced scheduled maintenance on our status page, status.illevante.com, for the evening of 19 November, from 15:30 to 21:00 UTC (7:30 pm to 1 am in Dubai), before the patched packages arrived.
  2. 02Patching: We installed the patched alt-php and ea-php packages for each branch once they reached the stable repositories, then restarted the PHP processes so the new code loaded.
  3. 03Verification: We did not stop at the version number: on the supported branches we matched the new versions, and on the older ones, whose version number stays the same, we matched the build numbers to CloudLinux’s announcements and read the CVE numbers in the packages’ changelogs. Then we made sure no PHP process was still running the old binary and no update was left waiting.
  4. 04Older branches: CloudLinux backported the fixes into end-of-life alt-php branches, so a site on PHP 7.4 stayed on 7.4, patched, with no forced upgrade that could break its code. These packages arrived last, and we installed every one of them.

Hosting customers needed to do nothing, and files, databases and email were not affected. And CloudLinux’s isolation limits the damage if an attack ever comes before the patch: whatever a successful exploit runs, it runs as the site account’s user, CageFS confines that user to a file system of its own so it cannot see other accounts’ files, and LVE caps each account’s CPU and memory.

If you have a CoreVPS with root access, PHP on it is yours: the commands and measures above are all you need, the Imunify360 + CloudLinux security bundle brings your server the same patched PHP packages we install, and our technical support team is with you around the clock if you want a hand.

08Three announcements in one month

Between 21 October and 19 November PHP announced and fixed the PHP2Shell flaws, then announced CVE-2026-115560 with no fix, then shipped today’s release, which closes it along with two paths left after the fix for CVE-2026-109619. Most of them share one pattern: a fatal error or an interruption leaves half-finished state that a later request on the same worker reads. So expect more rounds, and make responding to them a habit:

  1. 01A standing inventory: Know, for each server and container, the PHP version serving requests, its SAPI, where its package comes from and who updates it. An inventory built during a crisis arrives too late.
  2. 02Production settings: Start from php.ini-production rather than PHP’s built-in defaults: it sets zend.exception_ignore_args to 1, which on its own closed the path to a critical flaw today.
  3. 03A supported branch: 8.2’s support ends on 31 December 2026, so plan your move to 8.3 or newer now, or rely on a provider that patches your older branches.
  4. 04Restarting is part of updating: An update not followed by a restart of the workers is not finished, so put the restart in the same command rather than a step to remember later.

Test your understanding

Three questions, one minute

⁦0 / 3⁩Set 1

  1. 01Your server runs nginx and PHP-FPM with the usual setup that closes the FastCGI connection after each request. Where does it stand on the request-smuggling flaw?

  2. 02You updated to 8.3.37 and your application’s upload progress bar stopped working. What is the likeliest cause?

  3. 03A server on PHP 8.5.12 with php.ini-production settings. Which of those settings closes the path to CVE-2026-129474?

Ready to start? Power your projects today

Choose the hosting, server or domain that suits your business, and our specialist team is available around the clock to make your projects a success.

A .com domain a year
$17
cPanel hosting per month
$2
CoreVPS servers per month
$3.50