Live Updates
This is a developing story. We will add each update here as PHP publishes advisories, CVE identifiers, and fixed version numbers. Newest first.
| Time (UTC) | Update |
| 19 Nov | PHP has not yet published technical details, CVE identifiers, or fixed versions. CVE-2026-115560 is reported, not confirmed, to be part of this release. |
TL;DR: How to Prepare
On 18 November, the PHP security team announced security releases for Thursday, 19 November, between 14:00 and 14:30 UTC that cover all supported PHP versions. The highest severity issue is CRITICAL but it requires non-default configuration or uncommon setups.
Here’s what you should do:
- Plan to upgrade every supported PHP branch as soon as fixed versions appear on php.net, today between 14:00 and 14:30 UTC.
- Finish October first. If you are not yet on 8.5.12, 8.4.27, 8.3.36 or 8.2.35, the PHP2Shell fixes are still your top priority. Exploitation attempts against those flaws have been reported.
- Know your configuration. PHP says today’s critical issues need non-default or uncommon setups, so your exposure depends on how PHP is configured, not only which version your deployment uses.
Introduction: Four Weeks Later, the Alarm Rings Again
Less than a month after PHP2Noise sent security teams scrambling, PHP has issued another heads-up about a critical security release. The word “critical” will set off the same alarms. This time, though, the warning carries an important qualifier.
PHP says the critical issues require non-default configuration or uncommon setups. That does not make the release optional. It does mean the right first question is not “are we on PHP?” but “how is our PHP configured?”
Why the details are kept quiet
Last month’s PHP2Shell fixes arrived on an urgent, one-day turnaround. This release rides the regular cycle instead. That choice, together with the “non-default” qualifier, suggests PHP sees this as serious but still lower impact than in October.
PHP’s source code is public, so a fix committed to the public repository is also a map to the bug. To avoid that, PHP prepares security patches privately and publishes them together with the release.
The practical takeaway: before release, nobody outside the PHP security team and the reporters knows the full picture. Treat any “leaked details” accordingly.
The reported candidate: CVE-2026-115560
One issue expected in this release is already partly public. On 23 October, two days after PHP2Shell, PHP published an informational advisory for CVE-2026-115560. PHP called it an unlikely remote code execution vector in session upload progress. It said it would handle the fix in the regular release cycle and publish a full advisory with the next release. Today’s release is that next regular release.
Public analyses describe the trigger as a narrow chain of settings (details):
- The configuration sets session.serialize_handler to php_binary or php_serialize.
- The application switches it back to php with ini_set() at runtime, before calling session_start().
- session.upload_progress.enabled is still on, which is the default.
That chain fits PHP’s “non-default or uncommon” wording. But PHP has not confirmed that CVE-2026-115560 is the critical issue, or that it is the only one.
The interim mitigation
Last month followed the same script. On 20 October, PHP warned of an urgent release. On 21 October, it fixed CVE-2026-109618 and CVE-2026-109619, two pre-auth remote code execution flaws rated 9.2 on CVSS v4.0. In the day between, the internet filled the silence.
- Alleged PoCs appeared within hours. The ones we reviewed were partial or broken. Some fresh “exploit code” can also carry malware aimed at the researchers who run it.
- Fake mitigations circulated. Advice such as disabling unrelated session features spread widely. People involved with PHP pushed back that ini settings alone would not save users, and the official partial mitigations later proved incomplete.
- Teams spent effort on noise. Time went into chasing rumors instead of inventorying systems and preparing to patch.
The upcoming-patch notice dilemma
In PHP2Noise we argued that advance notices may now help attackers as much as defenders. A notice tells everyone where to look. With LLMs, attackers can mine recent commits, issues and discussions for leads far faster than before.
The notice still has real value: it lets administrators book a maintenance window – and today’s notice gives more to work with than October’s did. It names the condition (non-default setups), and one candidate issue already has a published mitigation. That is a better starting point for defenders. Use it, and ignore the rest until 14:00 UTC.
Part of a Wave: Why Critical Releases Keep Coming
Today’s release is not an isolated event. In barely a month, security teams have faced a run of critical fixes in software that runs much of the web.
| Date (2026) | Event |
| 19 Nov | PHP critical security release for all supported branches (today) |
| 23 Oct | PHP informational advisory for CVE-2026-115560, fix deferred to the next regular release |
| 21 Oct | Node.js security release: 10 CVEs, including CVE-2026-111497, a Brotli decoder RCE |
| 21 Oct | PHP2Shell fixed: CVE-2026-109618 and CVE-2026-109619, pre-auth RCE |
| ~21 Oct | eMudhra intermediate CA compromise forces certificate updates |
Discovery has sped up, and so have attackers
Part of the reason is that finding bugs has become faster and cheaper, with AI-assisted research turning up flaws in mature code. Exploitation has sped up too. According to the Cloud Security Alliance, AI can now generate working CVE exploits in 10 to 15 minutes for about $1, and median weaponization time has fallen to 1.6 days. Every process step between disclosure and deployed fix is exposure time the attacker gets for free.
The fatigue risk
Back-to-back emergencies wear teams down. The danger is that “critical” starts to feel routine, or that teams patch the newest alarm while older ones stay open. Do not let today’s release push October’s PHP2Shell fixes off the list.
How to Prepare Before the Release
You can do most of the work now, before a single detail is published.
- Find every PHP runtime. Check servers, containers and base images, managed hosting, and CI runners. PHP is usually installed at the operating-system or image level, so Software Composition Analysis (SCA) of your application dependencies will not see it. Use host vulnerability scanners, package inventories, container image scanning, or a simple php -v.
- Confirm the October fixes. Anything below 8.5.12, 8.4.27, 8.3.36 or 8.2.35 is still exposed to PHP2Shell. Patch that first.
- Flag unsupported versions. Versions before 8.2 are end-of-life and will not get today’s fixes, so plan their migration. PHP 8.2 itself reaches end of life on 31 December 2026.
- Review non-default settings. Look at php.ini, FPM pool files, and .user.ini or .htaccess overrides. Search code for runtime ini_set() calls, especially on session.serialize_handler. Note anything customized; it is your shortlist once PHP publishes the conditions.
- Apply the interim setting where it is safe. If no application depends on upload progress tracking, set session.upload_progress.enabled=0 administratively and restart PHP workers.
- Book the window. Reserve a tested maintenance slot and a rollback plan. If you use distro packages or community container images, track when they publish rebuilt versions; they can lag behind php.net.
- Watch the official sources only. That means php.net and the php-src security advisories. Do not run unofficial PoC code on production or personal machines.
Lower risk reports by Checkmarx Zero (and others)
Today’s security release includes two CVEs that we had also found on our own. Another researcher reported them first, so our reports were marked as duplicates.
Conclusion: Patch Fast, Trust Slowly, and Know Your Config
The lesson from this release is not “panic about PHP.” It is that severity labels alone no longer tell you what to do. Today’s critical issues may never touch a default installation, yet a single customized server could be fully exposed. The teams that move calmly this afternoon will be the ones who already know where PHP runs and how each instance is configured.
So change the habit, not just the version number. Build the inventory today, and keep it current, because PHP’s next regular release is only four weeks away and the wave is not slowing. When the details land, match the published conditions against that inventory and patch the exposed systems first. Until then, treat every unofficial PoC and mitigation tip as unverified.
Checkmarx Container Security can identify PHP packages with known CVEs in supported container images. Checkmarx One brings those findings into one independent pane with your code and supply chain risk, so each fix reaches an owner instead of a shared inbox. See Checkmarx One in action.
References
- PHP news archive, 2026: 18 November upcoming security release notice and 23 October informational advisory
- Cloud Security Alliance, “The Collapsing Exploit Window: AI-Speed Vulnerability Weaponization,” 2026
Vulnerabilities