Contact us
← CVEHit Business AdvisoryPHP session and PHP-FPM flaws (phpAfterShell) — CVE-2026-126714: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

PHP session and PHP-FPM flaws (phpAfterShell) — CVE-2026-126714, CVE-2026-129289, CVE-2026-115560: Business Triage9.2/10Critical · CVSS 4.0PHP (GitHub advisory)Fix availablePHP 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36CISA: phpAfterShellCVE.org sourceCISA: PHP-FPMCVE.org sourceCISA: session formatCVE.org sourceNo KEV: phpAfterShellChecked Nov 19No KEV: PHP-FPMChecked Nov 19No KEV: session formatChecked Nov 19

Update PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Research: primary sources retrieved November 19, 2026.

Check these three things.

  1. System owner: confirm each PHP install runs 8.5.13, 8.4.28, 8.3.37 or 8.2.36, or 8.6.0.
    Affected versions and fixes
    • PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security releases on November 19, 2026. PHP 8.6.0 came out the same day and its changelog lists the same fixes.
    • Each fix applies to its own branch. For example, 8.4.x before 8.4.28 needs 8.4.28.
    • The releases fix 17 PHP security advisories. Seven are rated Critical (CVSS 4.0 9.2), four High and six Medium by PHP.
    • Some advisories affect only newer branches. Two critical flaws (CVE-2026-129474 and CVE-2026-129182) affect PHP 8.5 only.
    • PHP 8.1 and older no longer receive updates from the PHP project. depthfirst says the official end-of-life mitigation branches 7.4, 8.0 and 8.1 are not affected by phpAfterShell, but PHP says older unsupported releases may be affected by CVE-2026-115560. Check your vendor for other builds.
    • A Linux distribution or hosting provider may ship the fix under an older-looking version number. Check its own notice.
    • Record for each server:
      • PHP version serving web requests, which can differ from the command-line version.
      • Source of that record.
      • Date checked.
  2. Operations owner: check three settings: whether sessions are stored in files, whether session upload progress is on, and whether the web server reuses PHP-FPM connections.
    When the risk applies
    • phpAfterShell (CVE-2026-126714) applies to the default file-based session handler (session.save_handler = files).
    • Session upload progress (session.upload_progress.enabled) is on by default in affected releases. depthfirst says it is the easiest path to the flaw. PHP says code execution also needs an interrupted session write and a suitable object chain in the application.
    • CVE-2026-115560 needs session upload progress plus two different session formats reading the same session store, for example an application that changes session.serialize_handler before session_start().
    • CVE-2026-129289 applies to PHP-FPM only when the web server reuses backend connections: nginx fastcgi_keep_conn on, Apache mod_proxy_fcgi enablereuse=on, a HAProxy FastCGI backend that keeps connections, or LSAPI. PHP says standard nginx and Apache setups that close the connection after each request are not affected by the demonstrated attack.
    • PHP's advance notice says the critical issues need either non-default configuration or uncommon setups. depthfirst says any application on an affected version with file-based sessions is exposed. Treat both as true until you check your settings.
    • The CVSS vector AV:N means network-reachable, including internal networks. It is not proof of Internet exposure.
  3. Security owner: check records for PHP worker crashes, unexpected files in the session folder, and unexpected processes started by PHP.
    What the records can show
    • Several flaws crash a PHP worker. Code execution runs with the PHP worker's permissions.
    • Records to review:
      • PHP-FPM, Apache and PHP error logs for worker crashes and segmentation faults.
      • Unexpected or unusually large files in session.save_path.
      • Unexpected processes started by the PHP worker account.
      • Unexpected outbound connections.
      • Web server logs for unusual multipart uploads with a PHP_SESSION_UPLOAD_PROGRESS field.
    • Limits:
      • Workers crash for unrelated reasons.
      • Clean records do not prove no attack happened.
      • Missing records leave the question open.

This is not an emergency for most sites, but update this week. Update PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. Move faster where PHP-FPM connection reuse is on.

Do Now

  • System owner: update PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36 on its current branch, then restart PHP-FPM or the web server.
    Proof the update is done
    • A reload may leave old PHP workers running. Restart so every worker runs the new build.
    • Completion evidence for each server:
      • PHP version serving web requests after the update.
      • Source of that record.
      • Date checked.
  • Operations owner: where the update must wait, turn off session upload progress and backend connection reuse until it is done.
    What to change
    • Set session.upload_progress.enabled = 0 in php.ini or the FPM pool, then restart every worker. depthfirst says this removes the easiest path to phpAfterShell, not the flaw itself, and PHP says it does not protect applications that put attacker-controlled data into sessions in other ways. It also removes the attack path for CVE-2026-115560.
    • Turn off nginx fastcgi_keep_conn or Apache enablereuse for PHP-FPM backends. PHP lists this as the interim step for CVE-2026-129289.
    • Confirm the application still works after each change.
  • Provider: ask each hosting or software vendor that runs PHP for you which PHP build it uses and when the fix ships.
    What to ask
    • Ask for:
      • The PHP version or package serving your sites.
      • Whether it includes the November 19, 2026 fixes.
      • The fix date.

Do Next

  • Security owner: recheck CISA, the KEV catalog and the PHP advisories for changes to the exploitation status.
    What to recheck
    • depthfirst says parts of its code execution chain, including the decoder and final heap layout, remain reserved for coordinated disclosure. Watch depthfirst and PHP for full details.
    • PHP 8.2 security support ends December 31, 2026. Plan a move to a newer branch.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

phpAfterShell: partially overwritten session files (CVE-2026-126714)

Original advisory →
Required conditions
PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 and 8.5 before 8.5.13, with the default files session handler. Attacker influence over session data, an interrupted session write and, per PHP, a suitable object chain in the application.
Reported outcome
PHP: code execution with the PHP worker's permissions, or corrupted session state. CVSS 4.0 9.2 Critical (PHP). Weaknesses named: CWE-367 and CWE-662. depthfirst, which reported it, says its full chain does not depend on an application-defined gadget class, and it is reserving the decoder and final heap layout for coordinated disclosure.

PHP-FPM request smuggling (CVE-2026-129289)

Original advisory →
Required conditions
PHP-FPM or LSAPI behind a front end that reuses backend connections, and an application path that opens php://input without reading it fully. Introduced in PHP 5.6.0.
Reported outcome
PHP: an unauthenticated attacker can forge a FastCGI request and run PHP code as the worker; changed settings can persist for later requests on that worker. Code execution through LSAPI is not established. CVSS 4.0 9.2 Critical (PHP). Weaknesses: CWE-444 and CWE-670.

Session serializer mismatch (CVE-2026-115560)

Original advisory →
Required conditions
Session upload progress on, a writer using php_binary or php_serialize, a reader of the same session using the php format, and a suitable object chain available to the reader.
Reported outcome
PHP: code execution, file changes, session corruption or denial of service. The report shows command execution with common library object chains (Guzzle, Monolog). CVSS 4.0 9.2 Critical (PHP). Weaknesses: CWE-20 and CWE-502. First announced by PHP on October 23, 2026.

Fix guidance

  • php.net: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 security releases and PHP 8.6.0, all November 19, 2026.
  • PHP 8 changelog: each release section names the CVEs it fixes.
  • The other 14 PHP advisories fixed by these releases: CVE-2026-129496 (Critical 9.2): timezone cache use-after-free; needs file error logging and a startup diagnostic; all branches; CVE-2026-129474 (Critical 9.2): magic method backtrace use-after-free; PHP 8.5 only; CVE-2026-129182 (Critical 9.2): fatal error backtrace use-after-free; PHP 8.5 only; RCE not demonstrated; CVE-2026-129481 (Critical 9.2): interrupted session shutdown use-after-free; 8.3 to 8.5; RCE not demonstrated; CVE-2026-128090 (High 7.7): PHAR OpenSSL signature downgrade; only apps that trust signed Phar archives; CVE-2026-128064 (High 8.2): mixed-case HTTPS and FTPS URLs sent in plaintext; CVE-2026-127960 (High 8.7): CPU denial of service from folded HTTP response headers; CVE-2026-129291 (High 8.8): PHP-FPM local privilege escalation; needs local code execution and catch_workers_output; CVE-2026-129506 (Medium 6.3): SOAP use-after-free (crash); CVE-2026-129501 (Medium 6.3): DOM saveXml() double free (crash); 8.4 and 8.5; CVE-2026-15353 (Medium 6.3): SOAP information disclosure; CVE-2026-129538 (Medium 6.9): php-cgi PATH_INFO out-of-bounds read and write (crash); CVE-2026-129292 (Medium 5.3): PHP-FPM status page cross-site scripting; CVE-2026-129438 (Medium 6.3): RFC 3986 URI serialization near 2 GiB input; 8.5 only.
  • The 8.5.13 changelog also lists CVE-2026-48841 for a bundled uriparser 1.0.3 upgrade. No CVE.org record was found for it on November 19, 2026.
  • The CVE-2026-115560 fix turns session upload progress off by default and rejects runtime session setting changes while it is on. An explicit setting that turns session upload progress on overrides the new default.
  • Exploitation status: CISA SSVC in all 17 CVE records, dated November 19, 2026: Exploitation none. None is in CISA KEV catalog 2026.11.18, checked November 19. No KEV entry and Exploitation none do not prove no attacks occurred.
  • Proofs: depthfirst published a harmless proof for CVE-2026-126714 that plants a plain object in a session; it is not a code execution exploit. CSIRT Italia lists a public proof of concept for CVE-2026-115560 and none for the other critical or high CVEs. This page links to no exploit code.
  • NVD status for all 17: Received (not yet analysed), checked November 19, 2026.

What IntegrityLab.ai can check

  • This advisory does not mean IntegrityLab.ai detects these PHP CVEs.
  • When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server details they return. This gives your administrator a starting point. It does not currently offer a validated check for these CVEs, a session or FastCGI flaw test, confirmation of a package's fixes, or proof of compromise.
  • A displayed PHP version is a clue, not proof of the installed build or fix status. Many servers hide it, and a missing version does not rule PHP out.

How to read the score

PHP (GitHub advisory) CVSS 4.0: 9.2 (Critical). Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…