PHP’s security team announced on November 18 that a critical security release is coming on Thursday, November 19, 2026, between 14:00 and 14:30 UTC. The release will patch vulnerabilities affecting every currently supported PHP version, 8.2 through 8.5, and the highest severity rating involved is critical. PHP has not yet published CVE numbers or fixed version numbers, saying those details will go out alongside the actual release.
What PHP’s Advisory Actually Says
The announcement itself is short. According to PHP’s own security archive, the releases are part of the project’s regular four-week release cycle, and the critical-rated issues “require either non-default configuration or uncommon setups.” That phrasing matters: it suggests the most severe bugs won’t hit every single install out of the box, but PHP isn’t naming which configurations are at risk until the patch lands.
There is no confirmed CVE tied to this specific release yet. The Hacker News’ coverage speculates the fix could relate to a session-handling bug the outlet wrote about in October, which can lead to remote code execution when an app switches its session.serialize_handler value mid-request with upload progress tracking enabled. That link is unconfirmed by PHP itself, so treat it as a lead to watch rather than a settled fact.
Who Needs to Pay Attention
Since the flaws affect every supported branch rather than one plugin or framework, this touches practically every PHP-based site, which means WordPress and WooCommerce installs along with custom PHP applications. Agencies managing client sites on shared or managed hosting should check whether their host auto-applies PHP point releases or whether someone needs to trigger the update manually once it ships later today.
If a critical issue does turn out to need an unusual configuration to exploit, most standard WordPress and WooCommerce setups may be lower risk than the “critical” label implies on its own. Still, PHP point releases on this cycle have carried real, actively exploited bugs before, so waiting weeks to patch isn’t a safe bet. A WooCommerce Development or WordPress Development audit is a reasonable way to confirm which PHP version a site is actually running and whether updates are applied automatically.
This is the kind of advisory that’s worth checking back on later today once PHP publishes the fixed version numbers and CVE details. For a sense of how the last cycle played out, our earlier coverage of PHP’s PHP2Shell emergency patches is a useful comparison: that release also started as a vague warning before the specifics came out.

