A serializer mismatch can change how data is read
CVE-2026-115560 affects PHP session upload progress. The PHP project says the feature can write attacker-controlled data with one session serialization format and later read it with another. The second decoder may interpret part of a session key as serialized object data. A suitable object gadget chain could then run code with the PHP worker’s privileges.
The issue depends on configuration and application behaviour. The PHP advisory lists fixes in versions 8.2.36, 8.3.37, 8.4.28 and 8.5.13. Unsupported PHP releases may also be exposed because the feature has existed since PHP 5.4.
Find upload progress and session settings
Check php.ini, application configuration and hosting control panels for session upload progress settings. Identify routes that accept large uploads and inspect how session IDs and upload status are handled. Review custom session handlers and any code that deserializes session values.
Do not rely on a web application firewall to correct a serializer mismatch inside the PHP runtime. Confirm the installed package with the operating system or hosting provider and identify whether the fix has been backported.
Patch and test upload workflows
Upgrade to a fixed PHP branch version. Restart every process that loads PHP and test file uploads, progress reporting and session persistence. Check whether the application has dependencies that rely on the previous runtime behaviour.
If upload progress is not needed, review whether the feature can be disabled safely. This can reduce exposure while preparing an update, but the fixed PHP release remains the required remediation.
