FrankenPHP use-after-free in putenv() during shutdown
Only affects FrankenPHP before 1.13.4 when an application calls putenv() during request shutdown, such as from a shutdown function, destructor, or session handler. Fixed in 1.13.4.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.13.4
- Who is exposed
- Not reported
Summary
Written by a model
FrankenPHP before 1.13.4 contains a use-after-free vulnerability that leaves a dangling pointer to a freed environment table when putenv() is called during request shutdown. Attackers triggering putenv() in shutdown functions, destructors, or session handlers can crash the process on the next getenv() call or leak previous request environment values.
What to do
Upgrade to a fixed version: 1.13.4.
Workaround: Don't call putenv() from shutdown functions, destructors or session handlers.
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-128015 (FrankenPHP before 1.13.4 Use-After-Free via putenv() During Request 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-128015 (entry last updated 2026-11-17):
Affected:
- Go package github.com/dunglas/frankenphp: fixed in 1.13.4
Fixed versions: 1.13.4.
Conditions (all must be true for the bug to be hit):
- Application calls putenv() during request shutdown, from a shutdown function, an object destructor, or a session write/close handler (source: https://github.com/php/frankenphp/security/advisories/GHSA-rgpj-f2qx-xwhf)
- Classic mode on every thread; worker mode when a worker script restarts (source: https://github.com/php/frankenphp/security/advisories/GHSA-rgpj-f2qx-xwhf)
- Crash case applies to a release build of PHP 8.5 with the default allocator (source: https://github.com/php/frankenphp/security/advisories/GHSA-rgpj-f2qx-xwhf)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Don't call putenv() from shutdown functions, destructors or session handlers. (source: https://github.com/php/frankenphp/security/advisories/GHSA-rgpj-f2qx-xwhf)
CISA KEV: CVE-2026-128015 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128015 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/frankenphp/security/advisories/GHSA-rgpj-f2qx-xwhf
- https://github.com/php/frankenphp/commit/ab174aa6c27738b9ee56c97ac276d152bfb38f5e
- https://www.vulncheck.com/advisories/frankenphp-before-1.13.4-use-after-free-via-putenv-during-request-shutdown
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-128015
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-128015"}.Affected versions
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- 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)
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 87 if added to CISA KEV
- Would score about 82 if CISA's SSVC rates exploitation active
- Would score about 62 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now4 days
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.51%
- Posted on X by cve.now Nov 13
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/frankenphp · Advisory GHSA-rgpj-f2qx-xwhf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128015 |
| Record | NVD · CVE-2026-128015 |
| Other links 2 | |
| Patch | GitHub · php/frankenphp · Commit ab174aa6 |
| Link | vulncheck.com · advisories/frankenphp-before-1.13.4-use-after-free-via-putenv-during-request-shutdown |
Questions about CVE-2026-128015
Is CVE-2026-128015 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A use-after-free bug in FrankenPHP triggered by putenv() during request shutdown can crash the whole process with a segmentation fault on the next getenv() or putenv() call. With USE_ZEND_ALLOC=0, the next request can instead read the previous request's environment value.
Source: github.com
Which versions are affected by CVE-2026-128015?
github.com/dunglas/frankenphp (Go): before 1.13.4.
Source: cve.now feed data
Am I affected, and how do I check?
Versions before 1.13.4 are affected, in classic mode on every thread and in worker mode when a worker script restarts. The setup needs code that calls putenv() from a shutdown function, an object destructor, or a session write/close handler; the crash case applies to a release build of PHP 8.5 with the default allocator. To check, look at the FrankenPHP version and search the application code for putenv() calls in those places.
Source: github.com
How do I fix CVE-2026-128015?
Upgrade to a fixed version: 1.13.4.
Source: cve.now feed data
Related
- CVE-2026-128014FrankenPHP 1.8.0 before 1.13.2 Out-of-Bounds Write via Bundled Brotli Decoder
- CVE-2026-128023FrankenPHP before 1.13.0 Authentication Bypass via Dot-Form Header Name Aliasing
- CVE-2026-24895FrankenPHP affected by Path Confusion via Unicode casing in CGI path splitting allows execution of arbitrary files
- CVE-2026-24894FrankenPHP leaks session data between requests in worker mode
- CVE-2026-128016FrankenPHP before 1.13.4 Use-After-Free of SplTempFileObject Streams in Worker Mode
- CVE-2026-128020FrankenPHP before 1.13.2 Denial of Service via Cyclic Array Conversion
No corrections so far. Something wrong on this page? Report an error.