Hack

PHP Critical Security Release: Prepare for CVE-2026-115560

PHP ships a critical security release for all supported branches on 19 November. Here is how to prepare and patch.

19 November 2026  ·  5 min read  ·  Anand

PHP Critical Security Release: Prepare for CVE-2026-115560

The PHP project has scheduled a security release for every supported branch on Thursday, 19 November 2026, between 14:00 and 14:30 UTC. The highest severity in the batch is rated CRITICAL. The PHP team says the critical issues need non-default or uncommon configurations, but PHP runs a large share of the web, and this comes only four weeks after the emergency PHP2Shell fixes. Anyone running WordPress, Laravel, Magento or custom PHP code should plan to update today. This post covers what is known, how to check whether you are exposed, and how to roll the update out safely.

What is being fixed

The PHP site does not list the full contents of the release yet. One issue is already public: CVE-2026-115560, a remote code execution flaw in session upload progress that PHP disclosed in an informational advisory on 23 October 2026. PHP said the full advisory would come with the next release. The 19 November release is the next one, so a fix is widely expected, but php.net has not yet tied the CVE to a specific version. Check the official changelog before you treat a server as fixed.

For context, the release follows several others:

  • 21 October 2026: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fixed CVE-2026-109618 and CVE-2026-109619 (PHP2Shell), which are critical unauthenticated RCE flaws. Attacks on those two flaws have been reported since then.
  • 26 October 2026: updated Windows builds shipped with Brotli 1.2.1 to fix CVE-2026-111497.
  • 19 November 2026: PHP 8.6.0 general availability is planned for the same day.

The October PHP2Shell patches do not fix CVE-2026-115560. A server on 8.4.27, for example, is still exposed if it meets the conditions below.

Are you exposed to CVE-2026-115560?

According to PHP’s advisory, an application is only vulnerable when all of these are true:

  1. The configuration sets session.serialize_handler to php_binary or php_serialize.
  2. The code then switches the handler to php with ini_set() before calling session_start().
  3. session.upload_progress.enabled is on. This is the default.

Most sites will not meet the first two conditions. On shared hosting, though, you rarely know what every customer’s code does. These commands help you check a server:

# Current serializer and upload progress settings (CLI view)
php -i | grep -E 'session.serialize_handler|session.upload_progress.enabled'

# Look for runtime switching of the serializer in web roots
grep -rn --include='*.php' "serialize_handler" /var/www /home/*/public_html 2>/dev/null

The CLI can load a different php.ini from PHP-FPM, so also check the pool files and the ini directory that each FPM service uses. A phpinfo() page served through the web server shows the values that are actually live. Delete that page as soon as you have read it.

Mitigate now, before you patch

PHP’s interim advice is to turn off session upload progress. If you already did this for CVE-2026-109619 in October, leave it in place. The setting has to take effect before PHP parses the request, so ini_set() and .user.ini files will not work. Set it in php.ini or in the FPM pool configuration:

; php.ini
session.upload_progress.enabled = 0

; or in an FPM pool file, e.g. www.conf
php_admin_value[session.upload_progress.enabled] = 0

Then restart PHP so the workers load the new value:

# Debian / Ubuntu (adjust the version)
sudo systemctl restart php8.3-fpm

# RHEL / Rocky / AlmaLinux
sudo systemctl restart php-fpm

Check the result through the web server, not just the CLI. The only thing you lose is the upload progress bar feature, which few applications use.

Rolling out the update

The new builds take some time to reach distribution and vendor repositories. Watch your package source and update as soon as the new build appears:

  • Debian/Ubuntu (distro or Ondřej Surý PPA/repo): sudo apt update && sudo apt install --only-upgrade 'php8.*'
  • RHEL/Rocky/Alma (AppStream or Remi): sudo dnf upgrade 'php*'
  • cPanel/WHM: EasyApache 4 ea-php packages update through the normal system update. Confirm the version of each ea-php you have installed.
  • Containers: rebuild images from the updated official php tags and redeploy. Do not just restart old containers.

After you update:

  1. Restart every PHP-FPM service and confirm the running version with php -v and through a web request.
  2. Check that the version matches the fixed release listed on php.net for your branch.
  3. Keep session.upload_progress.enabled=0 until you have confirmed the fix, unless you actually need the feature.
  4. Look for any server still on PHP 8.1 or older. These branches get no security fixes, so plan a migration.

If you also plan to move to PHP 8.6, keep it separate from the security update. Install the patched build for your current branch first, and test 8.6 on a staging site later.

How TechProvidence can help

Patching PHP across many servers, cPanel accounts or container fleets without breaking sites is routine work for us. We can check your servers for exposure, apply the mitigation, roll out the patched builds with minimal downtime, and plan upgrades off end-of-life PHP versions. Our managed server plans keep this going continuously. If you want help today, contact us.

Source: The Hacker News

Running into something similar?

We look after Linux servers, control panels and virtualization for businesses every day. If an update, vulnerability or outage here affects you, we can help.