PHP to patch critical flaws in all supported versions on 19 November
The PHP project has pre-announced a security release for 19 November, under a month after the PHP2Shell patches, with a critical remote code execution bug among the expected fixes.
By Mr Elite Published Updated 6 min read
- Severity
- High
- Status
- Reported by outlets
- Sources
- 3
- Last checked
Latest updates
- Security Affairs reported new specifics: the release is scheduled for Thursday 19 November, the October advisory date, the PHP2Shell CVE numbers and fixed versions, that CVE-2026-115560 is not fixed by the earlier updates, and that PHP 8.1 and older get no upstream fixes.
The short version
- PHP's security team scheduled releases for Thursday 19 November 2026, between 14:00 and 14:30 UTC, covering all supported PHP versions.
- The highest severity in the batch is Critical, but PHP says those issues need non-default configuration or uncommon setups.
- CVE-2026-115560, a remote code execution bug in session handling, is expected to be among the fixes, according to Security Affairs.
- The October updates for PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 do not fix CVE-2026-115560, Security Affairs reported.
- PHP 8.1 and older no longer receive upstream security updates, so users should check their vendor's coverage.
What happened
The PHP security team announced security releases for Thursday 19 November 2026, between 14:00 and 14:30 UTC, covering all supported PHP versions. Security Affairs reported the pre-release notice.
PHP's announcement said: "The issues rated CRITICAL require either non-default configuration or uncommon setups." Security Affairs reported that the release falls within PHP's regular four-week update cycle. PHP has not published vulnerability identifiers for the batch, or fixed version numbers, ahead of the release.
One fix expected in the batch is CVE-2026-115560, a remote code execution (RCE) flaw, meaning an attacker could run their own code on the server. Security Affairs described it as involving session handling, and said PHP warned of it in October, two days after releasing the emergency PHP2Shell patches.
According to Security Affairs, PHP published an advisory on 23 October describing the trigger conditions. An application must set session.serialize_handler to php_binary or php_serialize, change it to php at runtime with ini_set(), and do so before calling session_start(). Session upload progress must also remain enabled. PHP says the setup is unlikely to be used in practice.
The same advisory recommended disabling session upload progress until a fix arrives in a regular release. Security Affairs reported that CVE-2026-115560 is separate from PHP2Shell and is not fixed by the 21 October updates for PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Those emergency updates addressed CVE-2026-109618 and CVE-2026-109619, the two PHP2Shell flaws, which Security Affairs said let unauthenticated attackers execute code through crafted HTTP requests.
Why it happened
PHP has described the conditions for CVE-2026-115560 but not the full technical mechanism. The flaw needs an application to change its session serialisation handler while running, before the session starts, and to have upload progress tracking still switched on.
The wider batch of critical issues has not been itemised in any report, so it is not yet clear how many other flaws are included or what causes them. PHP has said technical details and fixed version numbers will be published alongside the releases.
How this kind of failure works
PHP stores session data, such as who is logged in, by turning it into a text or binary string. This is called serialisation. Different session handlers use different formats, and PHP reads the data back using whichever handler is active at that moment.
Problems appear when the format used to write data differs from the format used to read it. Picture a post room where letters are sorted by a label code. If the sorter changes to a different code book halfway through the day, some labels are read as something they were never meant to say. In software, a mismatch like that can let attacker-controlled input be treated as instructions or objects, which is how deserialisation bugs often turn into code execution.
PHP has not said this is the exact mechanism here, so treat it as the general class of failure rather than a description of CVE-2026-115560.
Bugs that need an odd configuration are still worth patching. Attackers scan for exactly those setups, and a codebase that calls ini_set() at runtime may match without anyone remembering it does.
Who is affected
PHP says the coming fixes cover all supported PHP versions. Anyone running a supported release on a web server, in a container or on shared hosting should expect to need an update. Security Affairs noted that PHP 8.1 and older no longer get upstream security updates, though some Linux distributions and commercial vendors backport patches. If you run those versions, check your vendor's coverage instead of assuming the upstream release protects you.
For CVE-2026-115560 specifically, you are exposed only if your application changes session.serialize_handler to php at runtime after setting it to php_binary or php_serialize, and session upload progress is still enabled. Search your code for ini_set calls touching session settings and check your php.ini values.
The risk in practice is code execution on the web server. None of the reports says CVE-2026-115560 is being exploited.
How to defend against it
Tick each step as you check it. Your progress is saved on this device.
What to learn from this
The concept: Attack surface reduction through configuration
Many critical flaws only work when a feature is switched on or used in an unusual way. Each optional feature you leave enabled, such as upload progress tracking, is another path an attacker can try.
Turning off what you do not use is a mitigation you can apply today, before a patch exists. PHP itself recommends this here.
The idea applies well beyond PHP: unused admin panels, debug endpoints and legacy protocols all widen exposure for no benefit.
Disable features you do not need, because a bug in an unused feature is a risk you carry for nothing.
Quick check
Sign in to earn 10 XP for a right answer
Why does PHP recommend disabling session upload progress before the patch arrives?
The flaw only triggers when upload progress is still enabled alongside other conditions, so switching it off blocks that path until the fix is installed.
Timeline
- 21 October 2026 PHP ships emergency patches for the PHP2Shell flaws, CVE-2026-109618 and CVE-2026-109619, in versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12, according to Security Affairs.
- Two days after the PHP2Shell patches PHP warns of CVE-2026-115560, according to Security Affairs.
- 23 October 2026 PHP publishes an advisory recommending that session upload progress be disabled until a fix ships in a regular release.
- Thursday 19 November 2026, 14:00 to 14:30 UTC Scheduled release of fixes for all supported PHP versions.
What is not known yet
- Which fixed version numbers will be released, since PHP has not yet published them.
- How many critical flaws are in the batch beyond CVE-2026-115560, and what causes each one.
- Whether CVE-2026-115560 is being exploited; none of the reports says so.
- Which configurations of the other critical issues are needed to trigger them.
Questions people ask
When will the PHP security update be released?
PHP's security team scheduled the release for Thursday 19 November 2026, between 14:00 and 14:30 UTC. It covers all supported PHP versions. Fixed version numbers and technical details are due to be published with the release.
What is CVE-2026-115560?
It is a remote code execution flaw involving PHP session handling, according to Security Affairs. It can be triggered only when an application changes its session serialisation handler to php at runtime before session_start() and upload progress is still enabled.
Did the October PHP2Shell patches fix CVE-2026-115560?
No. Security Affairs reported that the flaw is separate from PHP2Shell and is not fixed by the 21 October updates for PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. It is expected to be fixed in the November release.
How can I reduce risk before the patch is available?
PHP's developers recommend disabling session upload progress until a fix is available. Then upgrade promptly once the releases appear. If you run PHP 8.1 or older, check whether your vendor backports fixes.
Sources
- SecurityWeek: PHP Readies Critical Security Updates to Patch Another RCE Flaw
- The Hacker News: PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19
- Security Affairs: PHP Warns of Critical Flaws Ahead of November Security Release