PHP patches seven critical flaws that can lead to code execution
Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; several bugs need specific application conditions.
Use-after-free in PHP 8.5 shutdown backtrace handling
A fatal error while restoring modified INI settings during request shutdown can repopulate PHP's stored fatal-error backtrace after the executor is cleaned up. A later request on the same PHP-FPM or mod_php worker can then read that freed memory via an early diagnostic, causing corruption, worker crashes, and possibly remote code execution. Triggering needs per-path max_memory_limit or zlib.output_compression with output_handler, plus Apache per-directory config or a PHP_VALUE/PHP_ADMIN_VALUE from the front end. PHP 8.5 before 8.5.13 is affected.
What to do: Upgrade PHP to 8.5.13.
| Product | Affected | Fixed in |
|---|---|---|
| PHP | 8.5.* before 8.5.13 | 8.5.13 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; several bugs need specific application conditions.
Wiz reports no observed exploitation; PHP 8.1 and earlier receive no official fixes.
Fixed builds include PHP 8.6.0 and 8.5.13, plus 8.4.28, 8.3.37 and 8.2.36 for most issues.
The November 19 releases fix flaws that PHP says need non-default or uncommon setups, including session-handling remote code execution.
Fixed releases are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36; two issues can reach ordinary WordPress hosts.
Fixes are in 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; maintainers say the critical bugs need uncommon setups.
Today 915 readers · 1K views · 86 reads · all time 211K views