PHP local privilege escalation in epoll event handling
Affects PHP-FPM pools with catch_workers_output enabled on the epoll backend. Fixed in PHP 8.2.36, 8.3.37, 8.4.28 and 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
- Specific setups only
Summary
A use-after-free flaw in PHP-FPM's epoll handling in PHP from PHP Group can lead to local privilege escalation. A local attacker with low privileges who can run PHP code in an FPM worker can crash the master process or execute code with its privileges, commonly root, when catch_workers_output is enabled and the epoll backend is used.
Written by a model
Original description
PHP-FPM epoll use-after-free can lead to local privilege escalation.
When catch_workers_output is enabled and the epoll event backend is used, the PHP-FPM master can close a worker's output pipe in fpm_child_close() without removing the associated event, and the delayed cleanup can free the worker record while its epoll registration is still active. A later event is then dispatched through a pointer into freed memory. A local attacker who can execute PHP code in an FPM worker can crash the master or execute code with its privileges, commonly root. catch_workers_output is disabled by default but enabled in the official PHP-FPM Docker images.
This issue affects PHP versions from 8.1.20 through 8.1.34, from 8.2.7 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.1.20 to 8.5.x with PHP-FPM, catch_workers_output enabled and the epoll backend, such as official PHP-FPM Docker image users.
Not fixed by: Running the FPM master without root does not correct the use-after-free.
“>= 8.1.20, <= 8.1.34”
What to do
Check whether your setup matches what the bug needs.
The catch_workers_output setting is enabled for the affected pool. The epoll event backend is in use. PHP 8.1.20 to 8.1.34, 8.2.7 to before 8.2.36, 8.3.0 to before 8.3.37, 8.4.0 to before 8.4.28, or 8.5.0 to before 8.5.13.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-129291 (PHP-FPM epoll use-after-free can lead to local privilege escalation), 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-129291 (entry last updated 2026-11-20):
Affected:
- PHP Group PHP: from 8.1.20, through 8.1.34; from 8.2.7, 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):
- The catch_workers_output setting is enabled for the affected pool. (source: https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m)
- The epoll event backend is in use. (source: https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m)
- PHP 8.1.20 to 8.1.34, 8.2.7 to before 8.2.36, 8.3.0 to before 8.3.37, 8.4.0 to before 8.4.28, or 8.5.0 to before 8.5.13. (source: https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-129291 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129291 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-jm4m-qfqx-967m
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-129291
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-129291"}.Affected versions
- PHP Group PHPFrom 8.1.20 · through 8.1.34; From 8.2.7 · 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
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 if CISA's SSVC rates it automatable
Timeline
- cve.now early warning
PHP readies critical updates to patch RCE flaw CVE-2026-115560
1 day - CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-jm4m-qfqx-967m |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129291 |
| Record | NVD · CVE-2026-129291 |
Questions about CVE-2026-129291
Is CVE-2026-129291 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?
When catch_workers_output is enabled, the FPM master monitors pipes connected to worker stdout and stderr, and a use-after-free in that epoll path can be abused. An attacker who can run PHP code in an FPM worker can crash the FPM master or execute commands with the master's privileges, commonly root, which permits escalation from the pool user to root.
Source: github.com
Which versions are affected by CVE-2026-129291?
PHP: from 8.1.20 through 8.1.34; from 8.2.7 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
Am I affected, and how do I check?
Affected versions are PHP 8.1.20 to 8.1.34, 8.2.7 before 8.2.36, 8.3.0 before 8.3.37, 8.4.0 before 8.4.28, and 8.5.0 before 8.5.13. The bug only applies to an affected pool with catch_workers_output enabled while the epoll event backend is in use. To check, run php -v for the version and look for catch_workers_output in the FPM pool configuration.
Source: github.com
How do I fix CVE-2026-129291?
Upgrade to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13 on the matching release line. The facts name no fixed 8.1 release, since the 8.1 range ends at 8.1.34 with no fix listed, and no vendor patch ids are given.
Source: github.com
Related
- SZB-2fc055d03dStarted as this early warning
- CVE-2026-129289PHP-FPM request smuggling through an unread HTTP request body
- CVE-2026-129496Timezone cache use-after-free can lead to remote code execution
- CVE-2026-129481Use-after-free after interrupted session shutdown
- CVE-2026-126714Partially overwritten session files can lead to remote code execution
- CVE-2026-129474Use-after-free in magic method backtraces can lead to remote code execution
No corrections so far. Something wrong on this page? Report an error.