CVE-2026-115560: Session serializer mismatch can lead to remote code execution.

Critical CVSS 9.2

CVE id
CVE-2026-115560
Published
Last modified

Affected packages

PackageAffected versionsFixed in
PHP
Runtimes and servers
< 8.2.36
>= 8.3.0, < 8.3.37
>= 8.4.0, < 8.4.28
>= 8.5.0, < 8.5.13
8.2.36, 8.3.37, 8.4.28, 8.5.13

How to fix it

Upgrade PHP to the fixed release of the line you run: 8.2.36, 8.3.37, 8.4.28, 8.5.13.

php --version
  • Install the patched PHP release of your minor line (the php image tag or your OS packages) and restart PHP-FPM.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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 phpbinary or phpserialize 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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.