CVE
PHP memory corruption in session shutdown cleanup
Affects PHP 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13 when a session cleanup callback fails fatally and the script filename sits in request memory. Fixed in 8.3.37, 8.4.28 and 8.5.13.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.3.37, 8.4.28, 8.5.13
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.3.37, 8.4.28, 8.5.13.
Summary
PHP's session extension has a use-after-free flaw: if a fatal error occurs in an application callback during session shutdown, a stale pointer to the script filename can later be freed by another request handled by the same worker. An attacker who can trigger such a failing cleanup could crash the worker or corrupt memory, reaching it remotely without logging in, though it only applies when the filename sits in request memory, such as when the script is not cached by OPcache.
Original description
Use-after-free after interrupted session shutdown.
The session extension records the filename of the executing script when a session starts. If a fatal error occurs in an application callback while the session variables are destroyed at shutdown, such as stream_close() of a user-defined stream wrapper, the pointer is retained after the request memory is freed, and a later request handled by the same worker can free the stale string. An attacker who can trigger such a failing cleanup may crash the worker or corrupt memory; code execution has not been demonstrated. This requires the filename to be allocated in request memory, for example when the script is not cached by OPcache.
This issue affects PHP versions 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.3, 8.4 or 8.5 (e.g. PHP-FPM) with sessions, where scripts run uncached by OPcache and session cleanup callbacks such as stream wrappers can fail fatally.
Not fixed by: Enabling OPcache alone or disabling session upload progress does not fix it.
“Affected versions >= 8.3.0, < 8.3.37 >= 8.4.0, < 8.4.28 >= 8.5.0, < 8.5.13”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- 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
- Would score about 48 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 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-129481 (Use-after-free after interrupted session shutdown), 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-129481 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: 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.3.37, 8.4.28, 8.5.13.
Conditions (all must be true for the bug to be hit):
- PHP 8.3 before 8.3.37, 8.4 before 8.4.28, or 8.5 before 8.5.13 (PHP 8.2 lacks the affected field) (source: https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7)
- Application uses sessions and a callback fails fatally during session cleanup, e.g. stream_close() of a user-defined stream wrapper (source: https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7)
- Script filename is allocated in request memory, e.g. script not cached by OPcache (source: https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7)
- A later request must be handled by the same worker (source: https://github.com/php/php-src/security/advisories/GHSA-g3vh-838c-65v7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129481 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129481 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-g3vh-838c-65v7
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-129481
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-129481"}.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
Affected versions
- PHP Group PHP
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 2
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-g3vh-838c-65v7 |
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129481 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129481
Is CVE-2026-129481 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?
If a callback fails fatally during session cleanup, such as stream_close() of a user-defined stream wrapper, session shutdown aborts before a stored filename is released or cleared. A later request handled by the same PHP worker may then corrupt memory or crash that worker.Source: github.com
Which versions are affected by CVE-2026-129481?
PHP: 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
Am I affected, and how do I check?
PHP 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13 are in range. PHP 8.2 lacks the affected session filename field. The demonstrated setup uses sessions, has OPcache disabled so the filename is in the request heap, and has later requests reaching the same worker. The installed version can be checked with php -v, and OPcache status in the opcache.enable setting.}Source: github.com
How do I fix CVE-2026-129481?
Upgrade to the fixed release for the branch in use: PHP 8.3.37, 8.4.28 or 8.5.13 (or later).Source: github.com