CVE
PHP remote code execution in session file handling
PHP 8.2 to 8.5 using the default files session handler is exposed when attackers can influence session data and the app has a gadget chain. Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
PHP's default file-based session handler can leave a session file with a mix of new and old data if a write is interrupted, so an attacker who can influence session data may inject objects and, if the application contains a suitable gadget chain, run code on the server. The attacker can reach this remotely without logging in, though the attack depends on interrupting a write at the right moment.
Original 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 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.
Who should check
Teams running PHP 8.2-8.5 with the default files session handler, especially apps that store user-controlled data in sessions or have deserialization gadget chains.
Not fixed by: Disabling upload progress does not fix apps that independently store attacker-controlled session data.
“This affects the files session save handler, which is PHP's default.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126714 (Partially overwritten session files can lead to remote code execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126714 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.2.0, fixed in 8.2.36; from 8.3.0, fixed in 8.3.37; from 8.4.0, fixed in 8.4.28; from 8.5.0, fixed in 8.5.13
Fixed versions: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Conditions (all must be true for the bug to be hit):
- PHP 8.2, 8.3, 8.4 or 8.5 before the patched release on that branch (source: https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp)
- Attacker can influence session data (for example via session upload progress or large user-controlled strings stored in the session) and interrupt a write at a useful point (source: https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp)
- Application contains a suitable deserialization gadget chain for code execution (source: https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126714 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126714 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126714
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126714"}.Timeline
- cve.now early warning
PHP readies critical updates to patch RCE flaw CVE-2026-115560
1 day - CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- PHP Group PHP
From 8.2.0 · fixed in 8.2.36; From 8.3.0 · fixed in 8.3.37; From 8.4.0 · fixed in 8.4.28; From 8.5.0 · fixed in 8.5.13
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-fm2m-fjf5-v3cp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126714 |
| Record | NVD · CVE-2026-126714 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126714
Is CVE-2026-126714 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A session file can be only partly overwritten if a write is interrupted, leaving a corrupted file that may contain injected objects. If the application has a suitable deserialization gadget chain, this can lead to code execution with the privileges of the PHP worker. Session state can also be corrupted.Source: github.com
Which versions are affected by CVE-2026-126714?
PHP: from 8.2.0 before 8.2.36; from 8.3.0 before 8.3.37; from 8.4.0 before 8.4.28; from 8.5.0 before 8.5.13.Source: cve.now feed data
How do I fix CVE-2026-126714?
Upgrade to the patched release on the matching branch: 8.2.36, 8.3.37, 8.4.28 or 8.5.13 (or later).Source: github.com