Critical PHP2Shell: two unauthenticated RCE flaws in PHP itself. Fixes shipped on 21 Oct 2026. Check if you are affected →
← All news

PHP's Third Session Bug, CVE-2026-115560, Is Still Unpatched Three Weeks On — Keep session.upload_progress.enabled=0 in Place

As of November 14, 2026, PHP has not shipped a regular bugfix release since 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21, so CVE-2026-115560 — an unlikely but possible RCE in session upload progress — has no fix yet. PHP's advice is unchanged: set session.upload_progress.enabled=0 and restart every worker until the next regular release.

What is CVE-2026-115560?

On October 23, 2026, two days after the emergency "PHP2Shell" releases (PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing CVE-2026-109618 and CVE-2026-109619), the PHP project published an informational advisory for a third issue in the same area: session upload progress.

According to php.net, the bug can only be triggered by an unusual combination of configuration and code:

  1. session.serialize_handler is set to php_binary or php_serialize in the configuration, and
  2. the application switches it to php at runtime with ini_set() before calling session_start(), and
  3. session.upload_progress.enabled is still on (it is on by default).

Applications that never change the serialize handler at runtime are not exposed. Because PHP considers the setup unlikely in practice, it chose to fix the bug in the regular release cycle rather than with another out-of-band release, and said it will publish a full advisory with that release. Third-party trackers describe it as a use-after-free related to an incomplete fix for CVE-2026-109619; Amazon Linux rates it Important (8.1).

Why it still matters on November 14

The php.net news archive shows no regular bugfix release since October 21 — the only releases since then are PHP 8.6.0 release candidates (RC5 on November 5, RC7 on November 12) and updated Windows builds for the Brotli fix on October 26. PHP 8.6.0 GA is planned for November 19, 2026.

So for every supported branch, CVE-2026-115560 is still unfixed today. Distribution trackers agree: Amazon Linux lists its php8.2–8.5 packages as Pending Fix and its older php (Amazon Linux 2 core) and php8.1 packages as No Fix Planned.

What to do now

PHP, Red Hat and CERT-EU all give the same mitigation:

session.upload_progress.enabled = 0

Practical notes from Red Hat's bulletin (RHSB-2026-013):

  • Set it where applications can't override it — php.ini, a PHP-FPM pool, or php_admin_value in the Apache configuration. ini_set() and .user.ini are too late, because the setting must apply before request parsing.
  • Add the line explicitly. In many shipped php.ini files the directive is commented out and defaults to enabled; uncommenting the sample line may leave it on.
  • Restart, don't reload, every PHP-FPM / Apache worker.
  • Verify via a temporary phpinfo() page served by the web SAPI, not php -i, which shows the CLI configuration.
  • Audit .htaccess, vhost php_value and .user.ini files that might turn it back on.

The side effect: PHP's native upload-progress data in $_SESSION stops working. Upload progress bars driven by the browser (JavaScript/XHR) are unaffected. If you already applied this setting on October 21 as a CVE-2026-109619 mitigation, keep it — no further action is needed until the fix ships.

When the fix lands

Watch php.net for the next regular releases of the 8.2–8.5 branches. When they arrive, read the full CVE-2026-115560 advisory, update, restart all workers, and only then consider re-enabling upload progress if you actually use it. Servers on PHP 8.1 or older will not receive an upstream fix at all.


Running PHP 7.x or 8.1 that can't simply be upgraded? RescuePHP can audit your configuration for this and the PHP2Shell issues, backport security fixes to legacy builds, or plan a staged upgrade to a supported PHP version.