Check these three things.
-
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.
-
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.
-
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.