PHP will ship critical security fixes on November 19 — what to prepare before 14:00 UTC
PHP's security team has pre-announced fixes for all supported versions, with the worst rated critical but limited to non-default or uncommon setups. How to get ready.
The PHP security team has announced security releases for Thursday, November 19, 2026, between 14:00 and 14:30 UTC, fixing vulnerabilities that affect all supported PHP versions. The highest severity is rated critical. In its notice, published on November 18, PHP adds an important qualifier: the critical issues "require either non-default configuration or uncommon setups." Technical details and fixed version numbers will be published with the releases. The useful thing to do today is to get ready to patch quickly — and to find out whether your setup is one of the unusual ones.
What happened, in plain English
PHP runs a large share of the web, from WordPress and Drupal to Laravel apps and custom sites. Its maintainers ship regular releases every four weeks. This time they have flagged in advance that the regular release is a security release, and that one or more of the bugs it fixes is critical.
Pre-announcing a release without details is standard practice for serious bugs: it gives administrators and Linux distributions time to prepare, without handing attackers a description of the flaw before a fix exists.
This comes four weeks after October's emergency release for PHP2Shell (CVE-2026-109618 and CVE-2026-109619), two remote code execution flaws that affected essentially every PHP web server and that CISA has since listed as exploited. The difference matters: PHP is signalling that this round's critical issues need configurations most installations don't have.
There is one known loose end. On October 23, PHP published an informational advisory about CVE-2026-115560, a code-execution path in session upload progress that only appears when an application sets session.serialize_handler to php_binary or php_serialize and then switches it to php at runtime before session_start(). PHP said it would publish the full advisory for that CVE "with the next release." Whether it is among tomorrow's critical issues, PHP has not said.
Are you affected? What to do now
Everyone on a supported PHP version (8.2, 8.3, 8.4 and 8.5) should plan to update. The current releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35; tomorrow's versions will be newer. PHP 8.1 and older no longer receive fixes from the PHP project.
Today:
- Inventory every PHP installation, including the ones bundled in control panels, hosting images, vendor appliances and Docker images.
php -von the command line may not match the PHP that serves your web requests; checkphpinfo()or your FPM/Apache module version too. - Know where your updates come from. If you use a Linux distribution (Ubuntu, Debian, Red Hat and others), hosting provider or official Docker image, the fix will arrive as their package or image, possibly with a backported version number. Distributions typically receive PHP security patches in advance.
- Line up a fast path: a staging environment, a test run of your main applications, and a maintenance window for tomorrow afternoon (UTC) or the morning after.
- Keep October's mitigation in place. If you set
session.upload_progress.enabled=0for PHP2Shell or CVE-2026-115560, leave it until you have read tomorrow's advisories. - Check whether you're on PHP 8.2. It reaches end of life on December 31, 2026; plan the move to 8.3 or later alongside this update.
Tomorrow, after 14:30 UTC:
- Read PHP's advisories (linked from the php.net front page and the php-src GitHub security advisories) and check whether your configuration matches the critical issues' conditions. That tells you whether this is an urgent same-day patch or a normal one.
- Update, then restart PHP-FPM, Apache or whichever process runs PHP — a new binary does nothing for workers that are still running.
- Rebuild and redeploy container images that bundle PHP.
The expert view
"Critical, but requires non-default configuration or uncommon setups" is a deliberate signal, and it is a different message from October's. Then, PHP told everyone serving web requests to update immediately and gave a list of partial mitigations. Now it is telling administrators to prepare, while indicating that the worst issues will not reach a default installation. For most sites this should land as a prompt, routine update rather than an emergency — the exception being anyone whose setup matches the conditions in tomorrow's advisories.
The context explains the extra caution. PHP2Shell's details leaked a day before the patch, exploitation attempts followed quickly, and the flaws were later chained into attacks on network appliances that embed PHP. PHP's security team has also been unusually communicative since, publishing an informational advisory two days after the October release rather than waiting. Pre-announcing this regular release as a security one follows that pattern: more warning, less surprise.
The practical lesson from the last month is about speed rather than severity labels. Most PHP servers are patched through a distribution or a hosting provider, and the gap between "PHP released a fix" and "the fix is on your server" is where risk accumulates. Organisations that can move from advisory to deployed update within a day — and know which of their systems embed PHP without advertising it — are in a better position for this release and the next one.
Official sources
- Upcoming Critical PHP Security Release — PHP security team, November 18, 2026
- Informational advisory: Session upload progress — PHP, October 23, 2026 (CVE-2026-115560)
- Security advisory: Critical remote code execution vulnerabilities, update now — PHP, October 21, 2026 (CVE-2026-109618, CVE-2026-109619)
We will update this article with the fixed versions and vulnerability details once PHP publishes them.