PHP Security Update Overview
The PHP security team has issued a crucial warning concerning vulnerabilities impacting all supported PHP branches as of their November 19, 2026 security update. Among these, the most severe vulnerabilities have been classified as critical, prompting an urgent call for action.
Webmasters and hosting service providers are strongly advised to implement these updates without delay. Although these critical vulnerabilities require specific configurations or rare setups, potentially leaving some installations unaffected, the risk remains significant.
Details on the Latest PHP Releases
The recent security updates include PHP versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36. These updates are designed to patch existing branches, allowing administrators to apply fixes without transitioning to a new branch. The updates were scheduled to be released between 14:00 and 14:30 UTC, maintaining PHP’s standard four-week release cycle.
Coinciding with the planned release of PHP 8.6.0, this update primarily focuses on addressing security vulnerabilities, enabling teams to secure their current installations without the need for immediate upgrades to the newest version.
Focus on Specific Vulnerabilities
Among the vulnerabilities addressed is CVE-2026-115560, a remote code execution flaw linked to session upload progress. This feature permits real-time tracking of file uploads, which, under certain conditions, could be exploited by attackers to execute code remotely on the server.
Administrators with potentially affected setups are advised to disable the upload progress feature temporarily, using the configuration session.upload_progress.enabled=0. This recommendation specifically targets the upload progress flaw and does not apply universally to all issues identified in the November update.
Guidance for Administrators
The PHP security team has not specified every individual flaw or its severity level in their preliminary notice. Administrators must consult the PHP 8 changelog to determine applicable fixes for their specific branch and avoid assuming that all vulnerabilities affect their systems identically.
Updating should begin with systems exposed to the internet, followed by background processes, container images, and deployment pipelines using older PHP versions. Ensure updates are applied through standard package sources or coordinate with hosting providers for patched builds. After updating, PHP workers should be restarted, and the live version validated, as checking via php -v only confirms the command-line version.
These updates succeed the emergency PHP2Shell patches from October, which addressed separate vulnerabilities allowing unauthorized code execution. The current CISA alert pertains solely to the October issues, emphasizing that an October update does not cover November’s fixes.
Future Outlook and Recommendations
Users of PHP 8.2 face an additional deadline as this branch will reach its end of life on December 31, 2026. Immediate application of the November patch is advised, followed by testing for migration to a supported branch before the cessation of security updates for PHP 8.2.
Staying informed and proactive in addressing these updates is crucial for maintaining robust cybersecurity measures and safeguarding web applications against potential threats.
