Session serializer mismatch can lead to remote code execution
Get instant alerts when new vulnerabilities affect PHP - before attackers find them.
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 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.
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Generated by AI (claude-fable-5.1) and published by VulnTracker. It is not reviewed by a person, so check the vendor advisory before you act on it.
Upgrade PHP to 8.2.36, 8.3.37, 8.4.28 or 8.5.13 (or later on the same branch). On openSUSE Tumbleweed, update php8 to 8.5.13-1.1 or later.
A fix is recorded
Guidance updated 2026-11-20
Sign in free to see the steps, fixed versions and workarounds.
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
Get alerted
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
This product uses data from the NVD API but is not endorsed or certified by the NVD. CVE records are from the CVE Program (CVE.org).