PHP issues four security releases patching critical remote-code execution flaws
PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36 fix critical vulnerabilities that could enable remote-code execution, though exploitation requires non-default or uncommon configurations.
Summary
The PHP Project has released simultaneous security updates for four supported branches: PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36. Each version contains multiple security and bug fixes, with several rated critical severity due to their potential for remote-code execution. The project disclosed that all critical flaws depend on either non-default configuration settings or uncommon deployment setups, reducing immediate widespread risk but still demanding prompt attention from administrators running exposed PHP installations.
Linux distributions and downstream vendors are expected to publish updated packages shortly. Administrators should review their PHP configurations against the release notes and prioritize patching for internet-facing web servers, particularly those with customized or less common PHP setups that may fall within the affected scope.
Vulnerability scope and affected versions
- Affected branches: PHP 8.5.13, 8.4.28, 8.3.37, and 8.2.36 all receive security fixes, covering the currently supported release lines from the latest 8.5 series back to the older 8.2 LTS-adjacent branch.
- Critical severity: Multiple vulnerabilities in each release carry critical ratings due to remote-code execution potential, representing the highest severity class in PHP's security taxonomy.
- Exploitation prerequisites: All critical vulnerabilities require non-default configurations or uncommon operational setups, meaning stock PHP installations with standard configurations are not directly exposed.
- Release timing: The pre-release announcement was issued on November 18, 2026, with final builds published November 19, giving vendors a short preparation window for package builds.
Why it matters
PHP underpins a substantial portion of the web stack across Linux distributions, from WordPress and Drupal deployments to custom enterprise applications, making these updates relevant for hosting providers and system administrators regardless of distribution. The requirement for non-default configurations to exploit the critical flaws offers limited comfort, as production PHP environments frequently deviate from defaults for performance or feature reasons, and the breadth of supported branches means most active deployments require attention. Linux vendors' upcoming package releases will be the primary vector for most users to receive these fixes, reinforcing the importance of distribution-maintained PHP packages over manual installations in security-sensitive contexts.
What to do
- Update to PHP versions 8.5.13, 8.4.28, 8.3.37, or 8.2.36.
- Review the release notes to check if your specific configuration is affected by the critical vulnerabilities.
Original reference: lwn.net →