News
PHP shipped fixes for seven critical flaws that can run code.
PHP published security updates for seven flaws scored 9.2, including bugs that can run code on the server, plus a separate use-after-free scored 8.8 that can raise privileges on the same machine.

Impact
- What was impacted
- PHP builds fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0. Seven flaws are scored 9.2. CVE-2026-115560 is improper input validation that can run code, change files, corrupt sessions, or deny service, and it is fixed in all five builds. CVE-2026-129496 is a use-after-free that lets someone with no account crash PHP workers or run code as those workers, fixed in all five. CVE-2026-129289 is a mismatch in how a request is read that can run attacker-controlled PHP as the worker with no other person involved and with PHP left on its default settings, fixed in all five. CVE-2026-126714, which Depthfirst calls phpAfterShell, is a time-of-check time-of-use bug that can run code as the PHP worker, fixed in all five. CVE-2026-129182 is a use-after-free that can corrupt memory and may allow full remote code execution, described as the same class of bug as CVE-2026-109619, fixed in 8.5.13 and 8.6.0. CVE-2026-129474 is a use-after-free that can run code on PHP 8.5 and later, fixed in 8.5.13 and 8.6.0. CVE-2026-129481 is a use-after-free that can make session cleanup fail, corrupt memory, crash a reused worker, or potentially run code, fixed in 8.3.37, 8.4.28, 8.5.13, and 8.6.0. CVE-2026-129291 is scored 8.8, is a use-after-free that can raise privileges locally, and is fixed in all five builds.
- Who was impacted
- Operators on PHP 8.2.x, 8.3.x, 8.4.x, and 8.5.x, which the project told to move to these releases. phpAfterShell matters for applications on an affected version that store sessions in files. CVE-2026-129289 matters where a front end keeps the connection to PHP open and the application opens php://input without reading the whole body. The report names nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. CVE-2026-129291 matters only after code is already running in an FPM worker, on a pool with catch_workers_output enabled and the epoll backend.
- What you need to do
- Update 8.2.x to 8.2.36, 8.3.x to 8.3.37, 8.4.x to 8.4.28, and 8.5.x to 8.5.13. The fixed 8.6 build named in this release is 8.6.0. If you cannot patch phpAfterShell immediately, turn off session upload progress. That advice is for applications on an affected PHP version that use file-based sessions. The report does not say this setting closes the other flaws, and it does not report attacks in the wild.
The PHP Foundation released security updates for several critical flaws that can lead to remote code execution, including CVE-2026-115560. This report describes that bug as improper input validation that can run code, change files, corrupt sessions, or deny service. It is fixed in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0. An earlier PHP notice expected this security release to include CVE-2026-115560 and described session-serializer conditions. This report does not repeat those conditions. The same five builds also fix CVE-2026-129496, a use-after-free that lets an unauthenticated attacker crash workers or run code with their privileges.
CVE-2026-129289, also fixed in those five builds, comes from inconsistent reading of an HTTP request. Attacker-controlled PHP can run as the worker without another person taking part and without a non-default PHP setting. It still needs a front end that keeps the backend connection alive, and an application path that opens php://input without reading it fully. The setups named are nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI.
Depthfirst calls CVE-2026-126714 phpAfterShell. Running code as the PHP worker takes influence over the session data, an interruption at a useful point in the write, and an application with a suitable deserialization gadget chain. Depthfirst said an interrupted pwrite or ftruncate can leave a malformed session file that session_start later loads, which becomes a way to deserialize attacker-controlled data, and that chaining it with another PHP deserialization bug leads to remote code execution. It affects applications on an affected PHP version that use file-based sessions. If you cannot patch immediately, turn off session upload progress. This flaw is fixed in the same five versions.
Three more flaws scored 9.2 are fixed on a shorter list. CVE-2026-129182 can corrupt memory and may allow full remote code execution, in the same class as CVE-2026-109619. It is fixed in 8.5.13 and 8.6.0. CVE-2026-129474 can run code on PHP 8.5 and later. That depends on the application: enough control of request data to influence memory allocation, a reachable magic method, and a fatal error at the relevant point. It is fixed in 8.5.13 and 8.6.0. CVE-2026-129481 can make session cleanup fail and may corrupt memory, crash a reused worker, or potentially run code. It is fixed in 8.3.37, 8.4.28, 8.5.13, and 8.6.0. CVE-2026-129291, scored 8.8, can raise privileges locally. It needs code already running in an FPM worker, a pool with catch_workers_output enabled, the epoll event backend, and a way to manipulate worker lifetimes and keep inherited pipe descriptors. It is fixed in all five builds. People on existing 8.2.x, 8.3.x, 8.4.x, and 8.5.x releases are told to update to the latest version. The report does not say these bugs are being exploited.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to PHP security updates that fix seven flaws scored 9.2 and one flaw scored 8.8. Do not write or run an exploit, a proof of concept, or a request meant to trigger these bugs. Facts from the report: - Fixed builds named: PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0. - People on existing 8.2.x, 8.3.x, 8.4.x, and 8.5.x are told to update to the latest version. The report does not say these bugs are being exploited. - CVE-2026-115560 (9.2): improper input validation that can run code, change files, corrupt sessions, or deny service. Fixed in all five builds. This report does not restate session-serializer conditions from an earlier notice about the same CVE. Do not invent those conditions into a check unless a separate advisory in front of you states them. - CVE-2026-129496 (9.2): use-after-free. Someone with no account can crash PHP workers or run code as those workers. Fixed in all five builds. - CVE-2026-129289 (9.2): inconsistent interpretation of HTTP requests. Attacker-controlled PHP can run as the worker with no other person involved and without a non-default PHP configuration. It needs a front end that keeps the backend connection and an application path that opens php://input without reading it fully. Named examples: nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, and LSAPI. Fixed in all five builds. - CVE-2026-126714 (9.2), called phpAfterShell by Depthfirst: time-of-check time-of-use. Code runs as the PHP worker only with influence over the session data, an interruption at a useful point in the write, and an application with a suitable deserialization gadget chain. It affects applications on an affected PHP version that use file-based sessions. If you cannot patch immediately, turn off session upload progress. The report does not say that setting closes the other flaws. Fixed in all five builds. - CVE-2026-129182 (9.2): use-after-free that can corrupt memory and may allow full remote code execution, in the same class as CVE-2026-109619. Fixed in 8.5.13 and 8.6.0. The report does not list 8.2, 8.3, or 8.4 as fixed builds for this CVE. - CVE-2026-129474 (9.2): use-after-free that can run code on PHP 8.5 and later. It depends on the application and needs control over enough request data to influence memory allocation, a reachable magic method, and a fatal error at the relevant point. Fixed in 8.5.13 and 8.6.0. - CVE-2026-129481 (9.2): use-after-free that can make session cleanup fail and may corrupt memory, crash a reused PHP worker, or potentially run code. Fixed in 8.3.37, 8.4.28, 8.5.13, and 8.6.0. The report does not list 8.2 as a fixed build for this CVE. - CVE-2026-129291 (8.8): use-after-free that can raise privileges locally. It needs local code execution in an FPM worker, a pool with catch_workers_output enabled, the epoll event backend, and the ability to manipulate worker lifetimes and keep inherited pipe descriptors. Fixed in all five builds. Context: - What was impacted: PHP workers on the versions these releases replace, with different bugs applying to file-based sessions, persistent FastCGI-style front ends, or FPM pools. - Who should care: operators of PHP 8.2.x through 8.5.x, and anyone running a build this release replaces on the 8.6 line. - What to do: install the fixed build for the branch you run. Use the session-upload-progress workaround only as a stopgap for phpAfterShell. Do this in order. Ask before editing php.ini, pool configs, web-server configs, or restarting PHP workers. Prefer read-only inventory first. Do not write or run an exploit or a proof of concept. 1. Inventory - Record the PHP version on each host or image. Map 8.2.x to 8.2.36, 8.3.x to 8.3.37, 8.4.x to 8.4.28, and 8.5.x to 8.5.13. If the version is 8.6 before 8.6.0, the fixed build named here is 8.6.0. If the version is outside these lines, say this report did not name a fix for it. - Note whether sessions are stored in files. - Note whether session upload progress is enabled. The report says to turn it off if you cannot patch phpAfterShell immediately. It does not name the ini key in this write-up. If you are not sure of the directive, say so instead of guessing. - For CVE-2026-129289, record whether nginx has fastcgi_keep_conn on, Apache mod_proxy_fcgi has enablereuse=on, HAProxy FastCGI keeps backend connections, or the server uses LSAPI, and whether application code opens php://input without reading it fully. - For CVE-2026-129291, record whether any FPM pool has catch_workers_output enabled and uses the epoll backend. 2. Contain - If file-based sessions are in use and the fixed build is not installed yet, propose turning off session upload progress and restarting the PHP worker. Ask before applying it. State that this does not replace the update and is not described as a fix for the other CVEs. 3. Remediate - Plan the branch update listed above. Ask before installing or restarting. - Do not jump a site to a different major or minor line unless the operator asks. The report's fixed builds are the ones named for each line. 4. Verify - Confirm the running PHP version is the fixed build you intended. - If the workaround is still in place, record that, and say whether the patch has now made it unnecessary. 5. Report back - Versions found, which hosts use file-based sessions or a persistent FastCGI-style front end, what you changed, and anything still on an unfixed build. Do not invent CVEs, package versions, or exploit conditions. If a check needs access I have not given you, say what you need and stop.