CVE-2026-126714
CVE-2026-126714 is a critical-severity vulnerability in PHP Group PHP (CVSS 4.0 CVSS-B score 9.2), classified as CWE-367 (Time-of-check Time-of-use Race Condition). It is not in the CISA Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment rates its exploitation as none. As of 2026-11-22, EPSS estimates a 13.3% probability of exploitation in the next 30 days, in the 96th percentile of scored CVEs.
Updated
Description
Partially overwritten session files can lead to remote code execution. The files session save handler, which is the default, writes updated session data into the existing session file without first clearing it. If a write is interrupted, the file can contain the beginning of the new session followed by the end of the old one, and bytes of an ordinary string can later be unserialized as objects. An attacker who can influence the session data, for example through session upload progress, and interrupt a write at a suitable point may inject objects, which can lead to code execution when the application contains a suitable gadget chain. Session data can also be corrupted. 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- Its current EPSS score (13.3%) is higher than that of 28% of CISA KEV entries.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesIf CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 3 days and forensic triage 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 yes, technical impact total, 2026-11-20).
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.
If CISA adds the CVE to the KEV catalog, the timeline shortens.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| PHP Group | 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
6 linksVendor advisories
Other references
Record Details
- Published
- 2026-11-19
- Last updated
- 2026-11-22
- Assigner (CNA)
- php
- Credited to
- Leo Lin; Asahi; Ilija Tovilo; Arnaud Le Blanc
More from PHP Group
RCE via OOM corruption
RCE via stale global state
Argument Injection in PHP-CGI
Session serializer mismatch can lead to remote code execution
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.