Session serializer mismatch can lead to remote code execution. Session upload progress, when enabled, can store attacker-controlled data in a session key using the php_binary or php_serialize session serializer. If the same session is later read with the php serializer, because session.serialize_handler is changed at runtime or differs between applications sharing a session store, bytes inside the key can be passed to the unserializer. A remote attacker able to submit a multipart upload can inject objects, which may lead to code execution when the reading application contains a suitable gadget chain, or to session corruption or denial of service. This issue affects PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
https://github.com/yora1928/cve_2026_115560_by_yora
https://github.com/Pr0fEs0r-X/PHP-CVE-2026-115560-Cheker-v-1.0
https://github.com/renzi25031469/CVE-2026-115560
https://github.com/pkconcept/php-cve-fix
https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-130138
https://cert.europa.eu/publications/security-advisories/2026-018
Published: 2026-11-19
Updated: 2026-11-19
Base Score: 7.5
Vector: CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P
Severity: High
Base Score: 9.8
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Severity: Critical
Base Score: 9.2
Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Severity: Critical