PHP prepares critical security updates across supported versions

PHP maintainers have announced security releases for all supported PHP versions, scheduled for November 19, 2026, between 2:00 p.m. and 2:30 p.m. UTC. The project said the updates are part of its regular four-week release cycle and will address vulnerabilities whose highest severity is rated critical.
The advisory does not identify the full set of flaws or the affected versions in detail. It does state that issues assigned the critical rating require non-default configuration or uncommon deployment setups, a qualification that does not remove the need for administrators to review their environments and plan maintenance promptly.
Session configuration is central to an expected fix
The release is expected to include CVE-2026-115560, a remote code execution issue associated with a specific session-handling sequence. Exploitation requires an application to configure session.serialize_handler as php_binary or php_serialize, then change it to php with ini_set() before calling session_start().
Session upload progress must also be enabled, which is the PHP default. As an interim mitigation, PHP users were advised to set session.upload_progress.enabled=0 until the next regular bugfix release and restart PHP workers so the setting takes effect.
Recent PHP flaws have drawn attacker attention
The advisory follows October fixes for CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell. Those critical flaws enabled unauthenticated remote code execution through specially crafted HTTP requests and have since been subject to limited active exploitation.
Attackers targeted publicly accessible Palo Alto Networks management interfaces and Check Point Security Gateways in attempts to attack Active Directory and deploy backdoors. The operational relevance is reinforced by Amazon’s early PHP2Shell attack observation documenting an attempted PHP2Shell attack before public disclosure, while the new advisory again places PHP configuration and patch timing under scrutiny.
Hunt.io reported on October 30 that it had identified 616 PHP2Shell-related files across multiple hosts. The collection included shared exploit kits, cloned proof-of-concept code, custom heap exploits, scanners, and post-exploitation tooling. CrowdStrike said exploit developers were unlikely to produce one universal exploit that worked reliably across every affected PHP deployment.
Business implication
Organizations running PHP should identify internet-facing applications, check their session serialization and upload-progress settings, schedule the November 19 update window, and restart the relevant workers after configuration changes or patch deployment. This gives operations teams a defined path to reduce exposure while the project publishes the security fixes.

