Security alerts · November 19, 2026

PHP session flaw can lead to remote code execution under specific configurations

On November 19, 2026, PHP fixed critical flaw CVE-2026-115560 in its session handling. If upload progress tracking is enabled and sessions are written and read in different formats, a remote attacker may achieve code execution. Update to 8.2.36, 8.3.37, 8.4.28 or 8.5.13.

What happened

On November 19, 2026, the PHP project released security updates fixing a critical flaw, CVE-2026-115560, in its session handling module. A session is how a web application remembers a logged-in user or the contents of a shopping cart from one click to the next.

The bug involves a feature that tracks the progress of file uploads (session upload progress). If this feature is enabled and sessions are written and read in two different formats, an attacker can slip their own data into a session. According to PHP’s security advisory, under certain conditions this can lead to code execution on the server.

The Hacker News reports that this is one of several critical flaws PHP fixed in the same release, after the project gave advance notice. The issue was reported by Dvir Sasson of ZEST Security. PHP’s advisory stresses that it is a separate bug, distinct from CVE-2026-109619.

As of release, the flaw is not listed in the CISA KEV catalog, the list of vulnerabilities the US agency CISA knows are being actively exploited. The European vulnerability database EUVD (EUVD-2026-130138) does not report exploitation either.

Why it is dangerous

This is an unsafe deserialization flaw (CWE-502) combined with improper input validation (CWE-20). PHP stores session data as text in a particular format and “unpacks” it back into data, and possibly program objects, on the next request. There are several such formats. If one part of the system writes a session in one format and another reads it in a different one, the reader may interpret part of the text in a completely different way.

Think of one department filling in a form where fields are separated by commas, while another reads it as if they were separated by slashes. Someone who knows this can phrase one field so the second department reads it as a different instruction. In PHP, that instruction can be the creation of an object. If the application contains suitable classes (a so-called gadget chain), this can lead to commands running with the privileges of the PHP process. The advisory says the researcher demonstrated this using classes from the widely used Guzzle and Monolog libraries.

The attack works over the internet and needs no login or user interaction. The attacker only has to submit a form with a file upload. Success depends on configuration, though: upload progress tracking must be enabled, and sessions must be written and read in different formats. For code execution, the application reading the session must also contain suitable classes. Without them, the advisory says the attack can still lead to session corruption or denial of service.

CVSS is a severity scale from 0 to 10. The score of 9.2 (critical) was assigned by the PHP project itself using the newer CVSS 4.0. It reflects a network attack without login and serious impact on confidentiality, integrity and availability. The rating also notes high attack complexity and specific prerequisites. If an attacker does run code, they can read application data and alter the website with the privileges of the PHP process.

Who is affected

Affected are PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13. PHP’s advisory notes that upload progress tracking has existed since PHP 5.4.0, so older, unsupported releases that will not receive a fix may also be vulnerable.

PHP powers a large share of the web: shared hosting, company WordPress sites, online shops, intranets and internal tools. The environments at real risk are mainly:

  • servers with session.upload_progress.enabled turned on, which was the default in PHP versions so far
  • multiple applications, FPM pools, virtual hosts or command-line scripts that share one session store but use different session.serialize_handler settings
  • applications that change the session format in code before starting the session

The advisory points out that separate FPM pools do not automatically mean separate session storage. If everything that accesses the same sessions uses the same format, the mismatch does not occur. Updating is still worthwhile, because according to The Hacker News the same releases fix other critical flaws too.

How to check if you are affected

First, find out your PHP version. This command only prints it:

php -v

The command-line version may differ from the one your website uses. List installed PHP packages with the first command on Debian and Ubuntu, or the second on RHEL and similar systems. On shared hosting, the PHP version is shown in the control panel, usually under domain or PHP settings.

dpkg -l | grep php
rpm -qa | grep php

Next, check whether upload progress tracking is enabled and which session format is in use. The output reflects the command-line configuration. Your website may use different settings.

php -i | grep -E 'session.upload_progress.enabled|session.serialize_handler|session.save_path'

Website settings may also live in FPM pool configs, virtual hosts or application code. These commands only search for them:

grep -rn -E 'upload_progress|serialize_handler' /etc/php* /etc/apache2 /etc/httpd /etc/nginx 2>/dev/null
grep -rn 'serialize_handler' /var/www 2>/dev/null

If your version is below the fixed release and upload progress tracking is enabled, treat the server as potentially vulnerable. The real risk arises when parts with different session formats access the same sessions.

How to fix it

The fixed versions are PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13. According to The Hacker News, PHP 8.6.0 also includes the fix. PHP’s advisory says the fix disables upload progress tracking by default and, while the feature is enabled, rejects runtime changes to session settings. Recommended steps:

  • Inventory PHP versions and session settings on all servers, starting with those exposed to the internet.
  • If you cannot update right away, set session.upload_progress.enabled=0 in php.ini and in every FPM pool and virtual host that writes to the same session store. It must be set in server configuration, because calling ini_set() from the application is too late, according to the advisory.
  • After changing the configuration, restart PHP-FPM or the web server so the change takes effect.
  • Update PHP through your distribution’s package manager, or ask your hosting provider to move you to a fixed version.
  • After updating, check that no configuration explicitly enables the feature. An explicit setting overrides the new default.
  • If you run PHP older than 8.2, plan a move to a supported branch.

If you genuinely need upload progress tracking, PHP’s advisory requires everything that reads and writes the same sessions to use the same session.serialize_handler setting, even after the update. The fix does not enforce this across separate configurations. Put applications with different formats on separate session stores, and when changing a store’s format, migrate or expire old sessions instead of reading them with the new format.

What if you may already be compromised

The PHP project has not published specific indicators of compromise, and no exploitation of this flaw is known so far. If your server was vulnerable and reachable from the internet, it is worth checking. An attacker would act with the privileges of the PHP process, for example the www-data user. Look mainly at:

  • PHP error logs: repeated messages about corrupted sessions or unexpected PHP worker crashes
  • web server access logs: an unusual number of file upload requests to pages that do not normally handle uploads
  • new or modified .php files in web directories, especially in upload folders
  • unknown processes, scheduled tasks (cron) and network connections running as the PHP user
  • new administrator accounts in applications and on the system

If you find anything suspicious, do not delete it. Back up logs and suspicious files first. Bring in an incident response specialist, rotate database passwords and keys stored in application configs, and consider rebuilding the server from a clean backup.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.