PHP schedules critical security releases for all supported branches

PHP will ship fixes on 19 November between 14:00 and 14:30 UTC, including a remote code execution flaw in session upload progress that it disclosed in October.

SecurityPublished
What happened
PHP announced security releases for all supported versions, due on 19 November 2026 between 14:00 and 14:30 UTC, with the top severity rated critical.
What’s new
PHP says the critical issues need non-default configuration or uncommon setups, and fixed versions and details will arrive with the releases.
Why it matters
PHP administrators face another critical patch four weeks after the exploited PHP2Shell flaws, though known mitigations may already cover the publicly disclosed bug.

PHP's security team said on 18 November that it will ship security releases on 19 November 2026, between 14:00 and 14:30 UTC, covering every supported branch of the language. The highest severity among the fixes is rated critical, but the project says the critical issues only arise with non-default configuration or uncommon setups. Fixed version numbers and technical details are to be published with the releases, and PHP is urging users to be ready to upgrade quickly.

The flaw already disclosed

Only one of the bugs has been named publicly. CVE-2026-115560 is a remote code execution flaw in PHP's session upload progress feature. In a 23 October informational advisory, PHP said it would handle the issue in its normal release cycle and publish a full advisory for it with the next release. The Register and SecurityWeek both expect it to be fixed in this batch.

Triggering CVE-2026-115560 takes an unusual chain, according to PHP: an application must configure session.serialize_handler as php_binary or php_serialize, then flip the handler to php during execution using ini_set(), ahead of session_start(), while session upload progress stays enabled. PHP Foundation executive director Elizabeth Barron told The Register in October that the bug needs a combination of settings and code "which we do not expect to occur in practical use of PHP".

PHP's interim advice was to set session.upload_progress.enabled=0 until the fix arrives. That setting was already a listed mitigation for CVE-2026-109619, one of the October PHP2Shell flaws, and PHP says administrators who applied it then need take no further action. Apps that do not alter the handler at runtime can keep the feature on, the advisory adds.

Fallout from PHP2Shell

The release comes four weeks after PHP's 21 October emergency patches for CVE-2026-109618 and CVE-2026-109619, the critical pair known as PHP2Shell, fixed in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Unlike those, the November update is part of PHP's regular four-week schedule. The US Cybersecurity and Infrastructure Security Agency added both PHP2Shell flaws to its Known Exploited Vulnerabilities catalog on 26 October, The Register reports.

Accounts of when attacks started differ. SecurityWeek says exploitation began days before the patches were published. The Register says attackers took longer than some researchers expected to reverse engineer the fixes, and cites Israeli startup Dream, which says suspected Chinese attackers combined PHP2Shell with a Linux kernel privilege-escalation exploit to take over 25 servers from as early as 23 October.

Other dates to note

PHP's release candidate announcements say PHP 8.6.0, the first general-availability release of that branch, is also planned for 19 November. Separately, PHP says the 8.2 branch reaches end of life on 31 December 2026, after which it will receive no security fixes.