Zakroi Dyru
DangerCVE-2026-115560

CVE-2026-115560: Object injection in PHP sessions via upload progress

Published

Upload progress writes attacker data into the session using the php_binary or php_serialize serializer. If the session is later read with php, bytes from the key end up in unserialize. No authentication needed, via a multipart upload: RCE if the application has a gadget chain, otherwise session corruption or DoS.

Product
PHP Group PHP
Severity
Critical, CVSS 9.2
CVE published
November 19, 2026
Weakness
CWE-20, CWE-502
  • Network attack
  • No login needed
  • No user interaction

What is CVE-2026-115560?

Upload progress writes attacker data into the session using the php_binary or php_serialize serializer. If the session is later read with php, bytes from the key end up in unserialize.

Which PHP Group PHP versions are affected?

  • до 8.2.36
  • до 8.3.37
  • до 8.4.28
  • до 8.5.13

Why is it dangerous?

No authentication needed, via a multipart upload: RCE if the application has a gadget chain, otherwise session corruption or DoS.

How to fix CVE-2026-115560

  1. Update PHP to 8.2.36, 8.3.37, 8.4.28, 8.5.13 or later
  2. Make sure session.serialize_handler is the same across all applications sharing a session store
  3. Don't change session.serialize_handler at runtime via ini_set

Our Telegram channel posts breakdowns like this on patch day (in Russian) →

What if you can't update yet?

Disable session.upload_progress.enabled in php.ini if you don't need upload progress.

Is it exploited in the wild?

As of November 19, 2026, it is not in the CISA KEV catalog, so no attacks have been confirmed yet. This page will be updated if that changes.

The same update also fixes 6 more CVEs:

Sources

Written with AI assistance from CVE Program, CISA KEV and vendor advisory data. Always check versions against the linked sources. Found a mistake? Tell us on Telegram.