Skip to main content

Description

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.

Key Findings

as of 2026-11-22
All KEV statistics→
  • Its current EPSS score (71.1%) is higher than that of 57% of CISA KEV entries.

Severity

CVSS 4.0 · CNA · CVSS-B9.2 CRITICAL
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationnone
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
14 days
Asset not publicly exposed
Next upgrade
fix on system upgrade

If CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 14 days on other assets.

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable no, technical impact total, 2026-11-19).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised. Fix on system upgrade means remediating the next time the asset receives a scheduled major upgrade or rebuild.

If CISA adds the CVE to the KEV catalog, the timeline shortens.

Affected Products

ProductAffected versions
PHP Group
PHP
0 to <8.2.36
8.3.0 to <8.3.37
8.4.0 to <8.4.28
8.5.0 to <8.5.13

References

4 links

Record Details

Published
2026-11-19
Last updated
2026-11-22
Assigner (CNA)
php
Credited to
Dvir Sasson (ZEST Security); Frédéric Le Roch; Carlos Perez (Lazarus Technology); HarukaKaya; nvr0x5; Katika Mohaseen; Jackson Tai; Crain; Ilija Tovilo; Arnaud Le Blanc; Jakub Zelenka

More from PHP Group

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.