CVEHit Business Advisory by IntegrityLab.ai
What’s the evidence?
PHP session and PHP-FPM flaws (phpAfterShell) — CVE-2026-126714, CVE-2026-129289, CVE-2026-115560: Business Triage
The reported finding
- 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.
- 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.
- 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.
Sources and vendor guidance
← Back to article questions