PHP released significant security updates on November 19, 2026, addressing a total of 18 vulnerabilities, which includes seven critical bugs capable of allowing remote code execution across supported environments. These fixes followed an advance notice issued by PHP project maintainers on November 18, 2026, concerning weaknesses affecting all supported PHP versions under certain conditions.
The severity of these flaws is underscored by the potential impact, as successful exploitation could permit unauthenticated remote code execution, session corruption, denial of service, memory corruption, or local privilege escalation. Specific vulnerabilities identified include CVE-2026-109619 and CVE-2026-129289. CVE-2026-129289, for instance, is a request-smuggling vulnerability in PHP-FPM that permits unauthenticated attackers to execute PHP code on servers that reuse connections to PHP-FPM.
The underlying vulnerabilities stem from various technical issues. These include improper input validation that could result in code execution, a use-after-free vulnerability leading to memory corruption, and a Time-of-check Time-of-use (TOCTOU) flaw. Additionally, an inconsistent interpretation of HTTP requests vulnerability can allow code execution without user interaction, provided the system is configured with persistent backend connections.
The security patches are available for several supported versions, including PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, and 8.6.0. These updates resolve the identified issues, such as the use-after-free flaw impacting PHP 8.5 and later, and the request-smuggling vulnerability in PHP-FPM.
Security experts emphasize that the only complete mitigation against these risks is updating the PHP installation to one of the newly patched versions. Organizations must ensure they are running versions such as PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, or 8.6.0 to secure their systems against these critical flaws.
It is important to note that these vulnerabilities affect supported PHP versions only when specific conditions are met, which can include non-default configurations or uncommon setups. Systems utilizing web servers like nginx, Apache, or HAProxy with specific FastCGI settings must pay close attention to applying these updates promptly to prevent potential compromise.
Sources: