PHP Schedules a CRITICAL Security Release for November 19 With No CVEs or Versions Published
Security / news
PHP Schedules a CRITICAL Security Release for November 19 With No CVEs or Versions Published
The security team says the releases land between 14:00 and 14:30 UTC and cover all supported versions; the last critical batch scored 9.2.

Attackers cannot yet use what PHP will fix on Thursday, November 19, because nobody outside the PHP security team has the details. The team's November 18 notice schedules security releases for all supported PHP versions between 14:00 and 14:30 UTC, with a highest severity of CRITICAL.
That is the whole public record so far: no CVE identifiers, no CVSS score, no version numbers. The notice says those arrive with the releases.
What the notice says, and what it leaves out
The notice describes the release as part of PHP's "regular four-week release cycle". It says the CRITICAL issues "require either non-default configuration or uncommon setups", which is the precondition that decides who needs to hurry.
Missing from it: which components are affected, whether any bug is reachable without authentication, and whether the team will release early. In October the team added that it might ship sooner if a flaw became public or exploitation appeared, per its oss-security announcement relayed by Oracle's Alan Coopersmith. The November notice carries no such line.
What the last critical release looked like
The previous critical batch is a fair guide to the shape of the work. On October 21 PHP shipped 8.5.12, 8.4.27, 8.3.36 and 8.2.35 for two flaws, CVE-2026-109618 and CVE-2026-109619, each rated CVSS v4.0 9.2, according to Qualys.
| Item | October 21 release |
|---|---|
| Fixed versions | 8.5.12, 8.4.27, 8.3.36, 8.2.35 |
| CVSS v4.0 | 9.2 for both CVEs |
| Most urgent target | Apache mod_php, prefork MPM |
| Branches with no upstream fix | 8.1 and earlier, about 71% of 156 million installs with a known version, per Qualys |
Qualys reports that 109618 was demonstrated as remote code execution on mod_php with default limits, and that 109619 needed two requests on the same worker. We covered the follow-on attacks in the Check Point Gaia chain.
Why a 14:00 UTC window matters
A fixed release time compresses the exposure gap. Once the commits and version numbers are public, anyone can diff the source against the previous release and work out the bugs, which is why PHP publishes the fixes and the details together. The October batch followed that pattern: Qualys notes that exploitation of 109618 was demonstrated on stock mod_php defaults, so the interval between release and working exploit code is the number to watch. For a recent example of an exploited flaw getting a rapid government deadline, see CISA's three-day triage window and the UnrealIRCd hot patch.
What to do before 14:00 UTC
Nothing can be patched yet, so the work is preparation:
- Inventory which PHP branches you run. If any host is on 8.1 or earlier, there is no upstream patch to wait for.
- Check how your distribution ships PHP. Backported fixes often keep the old upstream version string, so read the vendor advisory, not
php -v. - Line up a restart window. PHP-FPM and mod_php workers need a restart to load a fixed binary.
The next fixed version numbers will be published with the releases on November 19, and CVE entries should follow. Anything claimed about the November bugs before then is a guess.
Sources
More in Security
- 01Windows Server 2028 Preview Hardens Server Core by Default in Build 29706, but NTLM Is Still OpenHundreds of settings are on from first boot, Microsoft warns Server 2025 workloads may break, and the 33 percent of servers still on 2019 are untouched.
- 02VicOne's 28 Robotics Zero-Days Come From a Sponsored Article With No CVE IDs and No Named ProjectsThe Tokyo security firm's count ran as paid content on IEEE Spectrum and The Robot Report. An independent March paper counted 38 flaws in three named consumer robots.
- 03Synology's Third Critical DSM Advisory in 62 Days Hits OAuth, and the Last Patch Does Not Cover ItCVE-2026-120382 scores 9.8 and needs no login. DSM 7.4 and 7.3 builds ending -2 and -6 fix it; 7.2 and 7.1 have none yet.
- 04Codex's Sandbox Uses Seatbelt, bubblewrap and MXC, and Lets Commands Read Broadly by DefaultOpenAI's Nov. 18 engineering post says writes are confined to the workspace and the network is off, while reads stay wide open.