PHP Releases Another Round of Security Patches, Including a Critical Remote Code Execution Bug
The PHP Foundation has released another batch of security patches covering all supported versions of the language, including at least one flaw rated critical. The fixes span five releases and address a large number of bugs and CVEs. For patch managers who hoped for a quieter week, this is more work.
A Wednesday advisory said the issues rated critical need either non-default configuration or uncommon setups. It urged PHP users to prepare to upgrade promptly once the releases became available. Unlike last month's critical PHP2Shell flaws, these issues were not leaked ahead of the fixes.
One of the bugs is a remote code execution flaw, tracked as CVE-2026-115560. The PHP Foundation earlier said it would not get an emergency fix because it needs a very unlikely combination of configuration and specific application code. An application would have to set session.serialize_handler to php_binary or php_serialize, then switch it to php at runtime before starting a session. The session upload progress feature must also be enabled. Until the regular release, the Foundation advised setting session.upload_progress.enabled=0 as a mitigation.
The urgency comes from recent history. In October, teams rushed to patch CVE-2026-109618 and CVE-2026-109619, together called PHP2Shell, in a language that runs on about 70 percent of websites. CISA added both to its Known Exploited Vulnerabilities catalog on October 26. Dream researchers reported that suspected Chinese attackers chained PHP2Shell with a Linux kernel privilege-escalation exploit to compromise 25 servers, including Palo Alto Networks firewalls linked to US government-affiliated organisations, as early as October 23. The attackers likely still have remote access to some of those networks.
Why it matters
Anyone running PHP web applications, including small businesses relying on hosting providers or off-the-shelf CMS platforms, faces a second patch cycle in weeks after PHP2Shell was exploited. The assumption that a flaw needing unusual configuration can wait is tested by how quickly the earlier bugs were weaponised, even though attackers were slower than expected to reverse engineer the fixes. Teams need a repeatable path for fast PHP updates and a way to check their configuration, not just their version numbers.
What to do
- Upgrade PHP to the newly released fixed version for your supported branch as soon as it is available.
- Set session.upload_progress.enabled=0 as an interim mitigation for CVE-2026-115560.
- Check applications for session.serialize_handler being switched to php at runtime with ini_set() before session_start().
- Confirm the October PHP2Shell fixes (CVE-2026-109618 and CVE-2026-109619) are applied on all servers.