The PHP Group says remote code execution is possible when an attacker influences session data and interrupts a write at a useful point. A suitable application gadget chain is also required. Session data corruption is another possible outcome.The PHP CNA published the record on 19 November 2026 and assigned a Critical CVSS 4.0 score of 9.2. The affected versions span four PHP branches, from 8.2 through 8.5. The rating describes potential impact; it does not establish that every PHP deployment is exploitable.
What it allows
How Does CVE-2026-126714 Work?
PHP's default files session save handler updates an existing session file without first clearing its old contents. If the update stops partway through, the file can retain a new prefix and an old suffix. A file lock prevents simultaneous session operations, but it does not make this interrupted write atomic.
When PHP later reads that mixed session, bytes originally stored as an ordinary string can be interpreted as a serialized object. The vendor says session upload progress is one possible source of attacker-influenced data; applications can also store user-controlled strings in sessions. The attacker must additionally cause a useful write interruption, and code execution needs a suitable object gadget chain in the application.
The PHP fix clears the file before replacement and aborts when clearing fails. An interrupted update can still lose session data, but the old suffix cannot survive to create this object-injection path. Our PHP security release coverage puts this fix in the wider release context. Teams can use Vulnerability Intelligence to organize affected assets and remediation priority.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 8.2.x | 8.2.0 to before 8.2.36 | 8.2.36 |
| 8.3.x | 8.3.0 to before 8.3.37 | 8.3.37 |
| 8.4.x | 8.4.0 to before 8.4.28 | 8.4.28 |
| 8.5.x | 8.5.0 to before 8.5.13 | 8.5.13 |
For distribution packages and custom builds, check the supplier’s advisory.
Applies to PHP's built-in files session handler. Check the effective web-worker version and session backend; distributor backports require separate vendor confirmation.
Which PHP Versions Are Affected by CVE-2026-126714?
The PHP advisory lists 8.2.0 to before 8.2.36, 8.3.0 to before 8.3.37, 8.4.0 to before 8.4.28, and 8.5.0 to before 8.5.13. The corresponding fixed releases are 8.2.36, 8.3.37, 8.4.28 and 8.5.13. This defect concerns the built-in files session handler; another session storage backend is outside this specific file-write defect.
Inventory web-facing PHP workers and determine whether each application uses the files handler. Record the running PHP version, not only a package inventory or CLI version. For distribution packages with backported fixes, verify the distributor's security update and the actual deployed build. Keep the result in the patch management record.
The vendor suggests disabling session upload progress administratively when it is unnecessary and limiting untrusted session data until the update is applied. Disabling upload progress removes one input path, but does not address applications that store user-controlled session strings themselves. An atomic replacement session backend can avoid this particular defect; upgrading PHP remains the vendor's recommended fix.
Timeline
- 2026-11-19
The PHP Group published its advisory and PHP CNA record for CVE-2026-126714.
- 2026-11-19
The PHP 8 change log listed the fix in releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13.
What to do
-
Inventory PHP session deployments
Identify web-facing PHP workers on affected branches and confirm the effective session save handler for each application. Record application owners and versions.
-
Apply the branch fix
Update PHP 8.2 to 8.2.36, 8.3 to 8.3.37, 8.4 to 8.4.28, or 8.5 to 8.5.13. For distribution packages, use and document the vendor-supplied security fix.
-
Verify running workers after rollout
Restart affected web workers and confirm their effective PHP version or documented backported build. Repeat the check after any rollback or redeployment.
-
Reduce exposure while patching
If upload progress is unnecessary, disable session.upload_progress.enabled administratively. Limit untrusted data stored in sessions; neither step replaces the PHP update.
-
Review session failures
Review PHP and application logs for unexpected session read failures or corruption on affected applications. This is a defensive review suggestion, not a vendor detection signature or proof of exploitation.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-126714 in Brandefense Atlas
The Atlas record of CVE-2026-126714: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-126714 affect every PHP session backend?
No. The PHP Group identifies the built-in files session handler as affected by this specific interrupted-write defect. Confirm the effective handler for each application.
Which PHP releases fix CVE-2026-126714?
The PHP Group lists 8.2.36, 8.3.37, 8.4.28 and 8.5.13 as the fixed releases. Verify the version running in web workers after deployment.
Is disabling session upload progress enough?
No. PHP says that removes one attacker-controlled input path, while applications may still store untrusted strings in sessions. Apply the fixed PHP release.
Does the 9.2 score mean code execution is automatic?
No. The vendor describes required control over session data, a useful write interruption, and a suitable application gadget chain before code execution is possible.
Sources
- Partially overwritten session files can lead to remote code executionPHP Group
- CVE-2026-126714 RecordPHP CNA via CVE Program
- PHP 8 ChangeLogPHP Group