PHP runs a huge share of the web, and the PHP team has just put a date on its next security drop. New releases fixing vulnerabilities in every supported PHP version are scheduled for Thursday, 19 November 2026, between 14:00 and 14:30 UTC. The highest severity rating in the batch is CRITICAL. The same day also carries the first stable release of PHP 8.6.0. Here is what is coming, why the critical rating deserves attention, and how to prepare your servers before the builds land.
What the PHP Team Announced
The PHP security team published a short pre-announcement on 18 November. The key points, in their words:
- The releases are scheduled for Thursday, 19 November 2026, between 14:00 and 14:30 UTC. That is an evening window in India, around 19:30 to 20:00 IST.
- They are part of PHP’s regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions.
- The highest severity among the fixes is CRITICAL.
- Technical details, CVE numbers and fixed version numbers will only be published alongside the releases, so there is no public patch to review yet.
The currently maintained branches are the 8.2, 8.3, 8.4 and 8.5 lines. If your servers run any of those, the fixes will apply to you. The Hacker News has picked up the advisory and notes that the flaws affect all supported versions, which is the part worth heeding: this is not a single branch problem.
Why the Critical Rating Matters
The PHP team has added an important qualifier: the issues rated CRITICAL “require either non-default configuration or uncommon setups”. That phrasing has two practical readings.
First, a default PHP install is less likely to be directly exploitable out of the box. Second, and more importantly, “uncommon setups” describes a lot of real production environments: shared hosts with custom ini overrides, legacy applications that change session handling at runtime, frameworks that enable optional extensions, and hardened servers like the ones running session tweaks for compliance. Non-default configuration is exactly the space where serious PHP bugs have landed before.
Recent history is a good guide here. In October 2026, PHP shipped emergency patches for two critical remote code execution flaws fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The team’s own guidance at the time was blunt: all PHP users were strongly encouraged to update immediately. Treat the 19 November batch with the same urgency until the full advisories let you confirm exposure.
The Session Upload Progress Fix Is Included
One item to watch in the release notes is the promised full advisory for CVE-2026-115560. The PHP team said in an earlier update that a complete write-up for this issue would be published with the next release, which is this one.
CVE-2026-115560 is an unlikely remote code execution vector tied to session upload progress tracking. It only triggers under an unusual combination: an application must set session.serialize_handler to php_binary or php_serialize in configuration, then switch it to php at runtime with ini_set() before calling session_start(), while session upload progress stays enabled.
If that describes your application stack, the team suggested setting session.upload_progress.enabled=0 as a mitigation until the bugfix release arrives. That mitigation was first listed in the GHSA-6wmf-4rv5-p3rp advisory for CVE-2026-109619 published on 21 October 2026. If you already applied it, keep it in place and no further action is needed. Thursday’s release should carry the full technical details.

The Last Security Cycle Shows Why Speed Matters
This is the third PHP security event in a month, and the pattern is worth understanding. On 21 October, PHP shipped emergency patches for two critical vulnerabilities that could allow unauthenticated remote code execution. Those fixes went out as PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and the team’s guidance was to update immediately.
Shortly after, the PHP team announced updated Windows builds with the same version numbers and a rebuild suffix. Those packages pulled in Brotli 1.2.1, fixing CVE-2026-111497, an out-of-bounds write in Brotli decompression. In PHP Windows builds the vulnerable decoder is reachable through the cURL extension when automatic HTTP response decompression is enabled. That setting is off by default in cURL, but applications and HTTP client libraries often turn it on.
The lesson from October applies on Thursday: the fixes are only useful once they run on your servers, and the gap between advisory and patch is exactly where attackers operate.
PHP 8.6.0 Lands the Same Day
19 November is not only a patch day. PHP 8.6.0, the next major version, is planned for general availability on the same date. The release candidate cycle reached RC7 in the run-up, and the PHP team has been clear that release candidates are for testing only and should never run in production.
For most teams the right sequence is simple: take the security releases for your current branch first, get stable, and treat 8.6.0 as a separate migration project with its own testing window. The upgrade notes and NEWS file published with the release will list the behaviour changes that matter for your codebase.
What to Do Before the Release Drops
- Inventory your PHP versions now. Run
php -von every web server, container image and CI runner. Note which of the 8.2 to 8.5 branches each one uses. - Book a maintenance window. The releases land in a 30-minute window on Thursday evening IST. Have staging patched and verified first, then roll to production.
- Keep the session mitigation in place. If you disabled
session.upload_progressin October, leave it off until you have read the CVE-2026-115560 advisory and confirmed the fix covers your configuration. - Watch for the full advisories. CVE numbers and exact fixed versions publish with the builds. Compare them against your extension set before declaring the job done.
- Do not jump to 8.6.0 in production yet. Patch your current branch, then plan the major upgrade separately.
- Check managed hosting panels. Shared and managed hosts often lag a day or two behind php.net. Open a ticket now if you need same-day patching.
Frequently Asked Questions
When is the PHP security release coming?
The PHP team has scheduled the security releases for Thursday, 19 November 2026, between 14:00 and 14:30 UTC, which is around 19:30 to 20:00 IST. Technical details and CVE numbers will be published at the same time as the builds.
Which PHP versions are affected?
All supported PHP versions are affected, which means the maintained 8.2, 8.3, 8.4 and 8.5 branches. The highest severity in the batch is rated CRITICAL, and the team says the critical issues require non-default configuration or uncommon setups.
Do I need to update immediately?
Plan to update as soon as the releases are out and your staging tests pass. The PHP team has strongly encouraged prompt upgrades, and the batch includes fixes rated critical. If you are running a non-default configuration, treat the update as urgent.
Is PHP 8.6.0 part of this security release?
PHP 8.6.0 is planned for general availability on the same day, 19 November 2026, but it is a separate major release. Apply the security fixes for your current branch first and treat 8.6.0 as its own upgrade project.
