Skip to main content
Menu
CVEs

CVE

PHP memory corruption via stale last_fatal_error_backtrace

Affects PHP 8.5.0 through 8.5.12 under PHP-FPM or mod_php, and only with specific memory-limit or output-compression settings plus a later request on the same worker. Fixed in 8.5.13.

CVE-2026-129182Published Updated Summary written by a model

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 8.5.13
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. PHP 8.5.x before 8.5.13 Running under PHP-FPM or mod_php Shutdown fatal error needs per-path max_memory_limit, or zlib.output_compression with output_handler conflicting settings A later request on the same worker must trigger a diagnostic before executor initialization (Apache per-directory config, or FPM frontend sending PHP_VALUE/PHP_ADMIN_VALUE)

Summary

A use-after-free flaw in PHP (from the PHP Group) lets an attacker corrupt memory, crash PHP-FPM or mod_php workers, and possibly run their own code. It can be reached remotely without logging in, but only on servers with specific per-path or per-directory configuration, where a fatal error during request shutdown leaves stale data that a later request on the same worker then uses.

Original description

Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown.

A fatal error raised while modified INI settings are restored during request shutdown can repopulate the stored fatal error backtrace after the executor has been cleaned up. The request memory is then freed, and a diagnostic emitted before executor initialization in a later request handled by the same PHP-FPM or mod_php worker can access the stale backtrace. The shutdown error requires per-path configuration of max_memory_limit, or of zlib.output_compression together with output_handler (which .user.ini can also set). The early diagnostic requires Apache per-directory configuration or, for PHP-FPM, a PHP_VALUE or PHP_ADMIN_VALUE parameter sent by the front end. This can cause memory corruption and worker crashes, and may allow remote code execution.

This issue affects PHP versions 8.5.* before 8.5.13.

Who should check

Teams running PHP 8.5.x before 8.5.13 under PHP-FPM or mod_php with per-path max_memory_limit or zlib/output_handler overrides, plus Apache per-directory config or FPM PHP_VALUE.

Not fixed by: PHP 8.5.12 only fixed the earlier generic case; it does not cover these shutdown scenarios.

“Affected versions >= 8.5.0, < 8.5.13”

github.com

cve.now Index

38Pcve.now Index 38 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, 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 whether your setup matches what the bug needs.

    PHP 8.5.x before 8.5.13 Running under PHP-FPM or mod_php Shutdown fatal error needs per-path max_memory_limit, or zlib.output_compression with output_handler conflicting settings A later request on the same worker must trigger a diagnostic before executor initialization (Apache per-directory config, or FPM frontend sending PHP_VALUE/PHP_ADMIN_VALUE)
  • Upgrade to a fixed version: 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-129182 (Use-after-free via repopulation of last_fatal_error_backtrace global after 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-129182 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.5.0, fixed in 8.5.13
Fixed versions: 8.5.13.
Conditions (all must be true for the bug to be hit):
- PHP 8.5.x before 8.5.13 (source: https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m)
- Running under PHP-FPM or mod_php (source: https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m)
- Shutdown fatal error needs per-path max_memory_limit, or zlib.output_compression with output_handler conflicting settings (source: https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m)
- A later request on the same worker must trigger a diagnostic before executor initialization (Apache per-directory config, or FPM frontend sending PHP_VALUE/PHP_ADMIN_VALUE) (source: https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129182 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129182 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-2fjv-p558-g82m
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-129182
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-129182"}.

Timeline

  1. cve.now early warning

    PHP readies critical updates to patch RCE flaw CVE-2026-115560

    1 day
  2. CVE published
  3. First seen by cve.now
  4. Posted on X by cve.now

Affected versions

  • PHP Group PHP

    From 8.5.0 · fixed in 8.5.13

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · php/php-src · Advisory GHSA-2fjv-p558-g82m
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129182
RecordNVD · CVE-2026-129182

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129182

Is CVE-2026-129182 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?

After PHP shuts down following a fatal error, a stored fatal-error backtrace global can be filled in again and later used after its memory is freed (use-after-free). This can corrupt memory and crash workers. The advisory says it could potentially lead to remote code execution, which was not demonstrated through these entry points.Source: github.com

Which versions are affected by CVE-2026-129182?

PHP: from 8.5.0 before 8.5.13.Source: cve.now feed data

Am I affected, and how do I check?

PHP 8.5.x from 8.5.0 up to but not including 8.5.13 is affected; running php -v shows the installed version. The bug also needs PHP-FPM or mod_php, a shutdown fatal error (for example from max_memory_limit set in both global and path-specific configuration, or conflicting zlib.output_compression and output_handler settings), and a later request on the same worker that triggers a diagnostic before executor initialization. That can happen through Apache per-directory config or an FPM frontend sending PHP_VALUE/PHP_ADMIN_VALUE.Source: github.com

How do I fix CVE-2026-129182?

Upgrade PHP to 8.5.13 or later, the first version outside the affected range. The facts list no workaround.Source: github.com

More CVEs