PHP Warns of Critical Flaws in All Supported Versions as Patch Day Set for 19 November
The maintainers of the PHP programming language have issued an advisory about an upcoming security release that fixes critical vulnerabilities. It is scheduled for 19 November 2026, between 2 and 2:30 p.m. UTC, as part of PHP's regular four-week release cycle. The flaws affect all supported PHP versions, and the highest severity is rated critical.
The maintainers noted that the critical issues need either a non-default configuration or an uncommon setup to be exploited. No further details were disclosed. The release is expected to include CVE-2026-115560, a remote code execution flaw that only works if certain conditions are met. As an interim mitigation, users are urged to set session.upload_progress.enabled=0 until the next regular bugfix release, and to restart the PHP worker so the change takes effect.
The warning follows closely on other PHP problems. About a month ago, PHP fixed two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, together tracked as PHP2Shell. They allow unauthenticated remote code execution through specially crafted HTTP requests. They have since been exploited in a limited way, targeting publicly accessible Palo Alto Networks management interfaces and Check Point Security Gateways, with attacks aimed at Active Directory and the delivery of backdoors.
Hunt.io reported on 30 October 2026 that it had found 616 PHP2Shell-related files, including shared exploit kits, cloned proof-of-concepts, custom heap exploits, scanners and post-exploitation tooling. Underground forum participants have also been seeking exploits and discussing whether circulating proofs-of-concept work. CrowdStrike said exploit developers are unlikely to create one universal exploit that works reliably across all affected PHP deployments. PHP also patched a critical Brotli flaw last month (CVE-2026-111497), an out-of-bounds write that could lead to arbitrary code execution. Users should apply updates as soon as they are available.
Why it matters
Any business running PHP-based websites or applications, including those on shared hosting or managed by third parties, is exposed because every supported version is affected. The advisory breaks the assumption that default configurations are safe enough to wait on, since the interim fix is a setting change you must make and apply with a worker restart. With PHP2Shell tooling already circulating and being exploited, attackers are actively looking for PHP weaknesses, so the gap before patch day is a real risk window.
What to do
- Set session.upload_progress.enabled=0 in your PHP configuration until the patched release is installed.
- Restart the PHP worker after changing the setting so it takes effect.
- Schedule the update for 19 November 2026 and apply it as soon as it is available.
- Check that Palo Alto Networks management interfaces and Check Point Security Gateways are not exposed to the public internet.