PHP has told its users to get ready. On 18 November 2026 the PHP security team posted a notice on php.net saying that security releases will ship on Thursday, 19 November 2026, between 14:00 and 14:30 UTC, and that the highest severity among the fixes is CRITICAL. The releases cover every supported PHP version, so almost every PHP site, store and application will be asked to update.
If you run Magento, WordPress, Laravel or any custom PHP application, this is the moment to get your house in order. The good news is that PHP gave advance warning, and that the project has already described the one issue it expects to fix, along with a stop-gap setting. The less comfortable news is that the technical details, affected versions and fixed version numbers are only published alongside the releases, so some of this story is still unwritten.
This guide separates what PHP has actually confirmed from what is still unknown, explains how it connects to the PHP2Shell flaws fixed in October, and gives you a practical preparation plan. It is the hub of a short series, and each part links to a deeper guide: the CVE-2026-115560 mitigation checklist, the Magento and WordPress action plan, and the PHP 8.2 end-of-life upgrade plan.
The short version
- When: Thursday, 19 November 2026, between 14:00 and 14:30 UTC. That is 7:30 to 8:00 PM in India (IST) and 9:00 to 9:30 AM US Eastern.
- Who is affected: PHP says the fixes address vulnerabilities affecting all supported PHP versions.
- How bad: The highest severity in the release is CRITICAL. PHP adds that the issues rated critical require either a non-default configuration or an uncommon setup.
- Why it is scheduled: The releases are part of PHP’s regular four-week release cycle, not an out-of-band emergency drop.
- What to do now: Apply the session upload progress stop-gap if it fits your setup, plan a maintenance window, and be ready to update as soon as the new versions appear.
- What is not public yet: The full list of CVEs, the affected version ranges and the fixed version numbers. PHP says technical details and fixed version numbers will be published alongside the releases.
What the PHP security team announced
The notice, titled “Upcoming Critical PHP Security Release”, sits in the 2026 news archive on php.net (entry dated 18 November 2026). In plain terms it says four things. A set of security releases is scheduled for 19 November. They belong to the normal four-week cycle. They fix vulnerabilities across all supported versions. And the worst of them is rated critical but needs a non-default configuration or an uncommon setup to be reachable.
PHP closes the notice by strongly encouraging users to prepare to upgrade promptly once the releases are available. Notice what it does not say: it does not name a CVE, it does not list affected versions, and it does not say how many vulnerabilities are involved. That silence is deliberate. Publishing details before patches exist would hand attackers a head start, which is why projects pre-announce a window and keep specifics back until the fix is out.
Several security outlets covered the notice the same day, including The Hacker News, and a write-up from Aikido that tracks the details as they develop. We treat php.net as the primary source throughout this article and mark where a point comes from a secondary report.
The one CVE already linked to this release
Although the 18 November notice names no CVE, PHP had already published an informational advisory on 23 October 2026 about a separate problem in session upload progress. In it, the project advised setting session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect against what it called an unlikely remote code execution vector. PHP also said it would handle the issue in the regular release cycle and publish a full advisory for CVE-2026-115560 with the next release.
The next regular release is the one scheduled for 19 November. Security reporters therefore expect CVE-2026-115560 to be part of it, and we have the same expectation. Keep in mind that this is an inference from PHP’s October wording, not something the 18 November notice states. PHP has not confirmed that CVE-2026-115560 is the issue rated critical, and as of this writing it has not published a severity score or affected versions for it.
PHP’s October advisory describes the trigger conditions. An application has to set session.serialize_handler to php_binary or php_serialize in its configuration, then switch the handler back to php at runtime with ini_set() before calling session_start(). Session upload progress must also still be enabled. Apps that never change the handler at runtime can keep the feature enabled, according to PHP. Our step-by-step mitigation checklist shows how to check each condition on your own servers.
How this connects to PHP2Shell
This release lands about a month after another critical round. On 21 October 2026 PHP shipped 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, widely called PHP2Shell. PHP’s pre-announcement for that release gave both a CVSS v4.0 score of 9.2, and its security advisory said to update now. The Hacker News reported limited active exploitation of those two flaws.
PHP also pointed to a third item in the same period: a Brotli decompression bug, CVE-2026-111497, fixed in Brotli 1.2.1. PHP’s 26 October note says updated Windows builds include the fix and that the issue is reachable through the cURL extension when automatic HTTP response decompression is enabled, which cURL does not do by default.
The practical lesson is simple. If you have not yet installed the October releases, do that first. Those versions do not wait for 19 November, and they close flaws that are already being exploited in a limited way. For a full breakdown see our guide, PHP2Shell explained: CVE-2026-109618 and CVE-2026-109619, and its companion on the impact of PHP2Shell on Magento and WordPress.
Who should worry most
PHP’s own wording is the best guide here. The critical issues are described as needing a non-default configuration or an uncommon setup, which means the typical, cleanly configured site is less exposed than the headline suggests. That is reassuring, but it is not a reason to relax, for three reasons.
- Sites that have been through years of agency hand-offs, plugin installs and performance tuning rarely stay at default configuration. Odd settings accumulate.
- Shared hosting and managed platforms often set PHP options on your behalf, and you may not know what they are until you check.
- Third-party code matters. Session handling is a favourite place for older extensions and plugins to experiment, and the October advisory shows that runtime changes to the session handler are exactly where this risk sits.
Our reading of the October advisory is that the unusual part of CVE-2026-115560 is the runtime switch of the session serialize handler. If your codebase never does that, PHP says you can keep upload progress enabled. If you do not know whether it does, the safest course until the patch lands is to turn upload progress off.
Your preparation plan before the release
- Inventory your PHP versions. List every server, container and CI image, and write down the exact PHP version and the SAPI (PHP-FPM, Apache module or CLI). Staging and production often differ.
- Install the October releases if you have not. Move to the patched builds for your branch: 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
- Decide on the upload progress stop-gap. If you are not certain your code leaves the serialize handler alone, set
session.upload_progress.enabled=0in php.ini or your FPM pool configuration and restart PHP workers so the change takes effect. - Search your code. Look for
session.serialize_handlerand forini_set()calls nearsession_start(), in your own modules and in vendor code. - Book a maintenance window. The release window ends at 14:30 UTC, so for teams in India the new versions should appear in the evening. Plan the rollout for a time when you can test and watch logs.
- Prepare staging. Have a staging environment that mirrors production so you can test the new PHP build with real extensions, themes and checkout flows before you promote it.
- Line up rollback. Keep the previous PHP package or container image available and confirm database and file backups are recent.
What to do once the releases are out
- Open the php.net news archive and the release announcements and read the full advisory text. Confirm which CVEs are fixed and which version numbers apply to your branch.
- Check whether PHP now provides a severity score and affected-version range for CVE-2026-115560.
- Update staging first, run your regression and checkout tests, then update production.
- Restart PHP-FPM or Apache so the new binary and configuration are loaded. A package upgrade that never restarts the workers leaves the old code running.
- Confirm the running version with
php -vand, for web requests, with a protected phpinfo page or your monitoring tool. The CLI and the web SAPI can use different builds. - Decide whether to keep the upload progress stop-gap. PHP’s October advice was to keep it until the next regular bugfix release, so follow the final advisory text.
If you run an older PHP version
PHP’s October advisory notes that PHP 8.1 and older no longer receive updates from the project. Sites on those versions cannot rely on a fix from upstream, and the right answer is an upgrade, not a workaround. Even supported branches are on a clock: the PHP 8.2.35 announcement says PHP 8.2 reaches end of life on 31 December 2026 and will receive no further security fixes after that date. If any of your projects are on 8.2, our PHP 8.2 end-of-life upgrade plan walks through choosing a target version and sequencing the move. For Magento stores specifically, see PHP 8.5 and Magento 2.4.9: are you upgrade-ready?.
What it means for Magento and WordPress
Magento stores keep customer sessions in files, Redis or a database depending on how they are set up, and WordPress core does not rely on native PHP sessions although many plugins and themes do. That difference changes how you audit exposure and how you test the update. We cover both in PHP November 19 security release: what Magento and WordPress owners should do, including what to check in extensions and what a safe rollout looks like.
A timeline of PHP’s recent security communications
It helps to see the last few weeks in order, because the November release only makes sense as part of a sequence. Every date below comes from php.net’s 2026 news archive.
- 20 October 2026: PHP pre-announces a critical security release for 21 October, covering two vulnerabilities each rated CVSS v4.0 9.2.
- 21 October 2026: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 ship, together with an advisory for CVE-2026-109618 and CVE-2026-109619 that says to update now.
- 23 October 2026: an informational advisory recommends disabling session upload progress as a precaution and says a full advisory for CVE-2026-115560 will follow with the next regular release.
- 26 October 2026: updated Windows builds (the “-1” rebuilds) bundle Brotli 1.2.1 to fix CVE-2026-111497.
- 18 November 2026: PHP announces the security releases scheduled for 19 November, between 14:00 and 14:30 UTC.
- 19 November 2026: the release window itself.
One more detail from the same news archive is worth separating from the security story. PHP’s release candidate notices for PHP 8.6.0 say the first general availability release is planned for 19 November 2026 as well. A new major feature release and the security fixes for existing branches are different things. For most production sites the task on 19 November is to patch the branch you already run, not to jump to a brand new version on launch day.
Common mistakes to avoid during a PHP security update
- Updating the CLI but not the web SAPI. Running
php -vin a terminal tells you about the command-line binary. Your site may be served by a different PHP-FPM version. - Forgetting to restart workers. PHP-FPM and Apache keep the old code in memory until they are restarted or reloaded. The advisory-recommended setting only takes effect after workers restart.
- Setting the stop-gap in the wrong place. A runtime
ini_set()call is the wrong tool for this setting. Put it in php.ini or the FPM pool configuration, as PHP’s advisory describes, so it applies before PHP handles the request. - Skipping staging. A new PHP build can expose deprecated behaviour in older extensions. Test checkout, login, admin and any file upload flows before production.
- Patching only the main site. Staging servers, preview environments, cron containers and forgotten sub-sites are common blind spots, and they often share production credentials.
- Treating a stop-gap as a fix. Disabling upload progress reduces exposure to one known vector. Only the updated PHP version addresses the underlying flaw.
A simple testing routine for the new PHP build
Once the new versions are out, keep testing short and repeatable. Spin up a staging copy on the new PHP build, load your homepage, category and product or post templates, log in as a customer and as an admin, place a test order or submit a test form, upload a file, and run your scheduled jobs once. Watch the PHP error log and the web server log during the run. If anything fails, compare the error against the extension or theme involved before you blame the PHP update itself. Teams that script these checks can turn a stressful release evening into a thirty-minute routine.
How WebbyTroops can help
If you would rather not do this alone, our team handles PHP and platform security work for Magento and WordPress stores every week. Our Magento security patch installation service covers patching and verification, the Magento 2 update service covers version and PHP upgrades, and a Magento code audit can find risky runtime configuration in custom and third-party code before an attacker does.
Frequently asked questions
What did PHP announce on 18 November 2026?
It announced security releases for Thursday, 19 November 2026, between 14:00 and 14:30 UTC, covering all supported PHP versions, with the highest severity rated critical.
Is this an emergency out-of-band release?
No. PHP says the releases are part of its regular four-week release cycle, although the notice is titled as a critical security release.
Is CVE-2026-115560 confirmed as part of the November 19 release?
Not in the notice itself. PHP said in October that it would publish a full advisory for CVE-2026-115560 with the next regular release, and security reporters expect it on 19 November. Confirm it against the release advisory.
Do I need to disable session upload progress?
PHP advised setting session.upload_progress.enabled=0 until the next regular bugfix release as a precaution. Apps that never change the session serialize handler at runtime can keep the feature on, per PHP. If you cannot verify that, disabling it is the lower-risk choice until you have updated.
Should I wait for the new versions before updating anything?
No. If you have not installed the 21 October releases that fix PHP2Shell, do that now. Then apply the new versions as soon as they are published.
Which version numbers will fix the new issues?
PHP has not published them yet. It says fixed version numbers will be released alongside the updates, so check the official release announcements.

