PHP security updates: risk depends on configuration

Contents
At a glance
PHP released security fixes on November 19. Two advisories show why affected versions, server configuration and confirmed consequences must be checked separately.
Four maintained branches receive fixes
The PHP project released security updates 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19, 2026. Its announcements encourage users of each branch to upgrade. These releases matter to operators of websites and web applications that process untrusted requests, including customer portals and administrative services.
The project's advance notice said the highest severity was critical, while warning that the critical issues required non-default configuration or uncommon setups. The individual advisories explain those conditions. A critical rating therefore should not be turned into a claim that every PHP website has the same exposure or has already been compromised. [1]
A backtrace flaw has specific conditions
One advisory, GHSA-8mjj-2r7p-4hg2, describes use-after-free when PHP collects arguments from magic method calls for a backtrace. It lists PHP 8.5.0 through versions before 8.5.13 as affected. The demonstrated remote attack requires both fatal_error_backtraces=1 and zend.exception_ignore_args=0, along with a suitable application path.
PHP says its php.ini-production configuration excludes arguments and prevents that demonstrated path. The advisory also says no attacker-controlled remote trigger has been established for the underlying error in PHP 8.2–8.4. Those branches are outside this particular advisory's affected range; that does not mean they need no security updates.
Administrators should check the configuration actually used by web workers, including overrides. The advisory explicitly warns that changing only the command-line configuration is insufficient. It also distinguishes reachable framework methods from demonstrated exploitation of a complete framework installation. [2]
PHP-CGI is a separate case
A second advisory, GHSA-5j3f-64r7-f564, concerns PHP-CGI path correction. It describes crashes, possible disclosure through exposed path values, and memory corruption. PHP-FPM is unaffected by this specific issue. The advisory says code execution has been claimed but not confirmed, so it would be misleading to report proven remote code execution for this flaw.
The practical next step is to identify the deployed branch and server interface, then obtain the appropriate fixed package through the official project or the operating-system vendor. Distribution backports and their availability were not checked in this report. The two advisories are primary documents from the same project, not independent corroboration. This report does not establish exploitation in the wild, a breach of any named website or a cryptocurrency loss. [3]
Evidence & sources
Source record: · Checked:
Record limits · PHP released security fixes on November 19. Two advisories show why affected versions, server configuration and confirmed consequences must be checked separately.
- Source reported
PHP announced security releases on November 19.
Supporting excerpt: PHP security release announcements
This is a security release.
PHP security release announcements ↗ - Source reported
The demonstrated backtrace attack requires two configuration settings.
Supporting excerpt: PHP: magic method backtrace advisory
The demonstrated remote attack requires fatal_error_backtraces=1 and zend.exception_ignore_args=0.
PHP: magic method backtrace advisory ↗ - Source reported
PHP-FPM is unaffected by the specific CGI issue.
Supporting excerpt: PHP: CGI path correction advisory
PHP-FPM remains unaffected.
PHP: CGI path correction advisory ↗


