PHP's November security release, published November 19, fixes seven flaws rated critical at CVSS 9.2, and by the maintainers' own account every one of them needs a non-default configuration or an uncommon setup to reach. That caveat is what separates this round from October's PHP2Shell, the pair of remote code execution bugs (CVE-2026-109618 and CVE-2026-109619) that attackers hit en masse and that drew comparisons to Log4Shell.
The patches cover every supported branch: 8.2.36, 8.3.37, 8.4.28, and 8.5.13. PHP 8.6.0, the new major release, shipped the same day with the fixes already in.
The seven critical bugs:
- CVE-2026-115560, session serializer mismatch RCE
- CVE-2026-126714, RCE in the file-based session handler
- CVE-2026-129289, PHP-FPM request smuggling via an unread HTTP request body
- CVE-2026-129496, timezone cache use-after-free RCE
- CVE-2026-129474, use-after-free in magic method backtraces
- CVE-2026-129481, use-after-free after an interrupted session shutdown
- CVE-2026-129182, use-after-free via repopulation of the last_fatal_error_backtrace global after shutdown
Maintainers published workarounds for all of them except CVE-2026-115560, but those are temporary mitigations, not a substitute for upgrading.
Which bugs to patch first
Upwind's analysis puts CVE-2026-129289, the PHP-FPM bug, at the front. It gives an unauthenticated attacker PHP code execution with a single request, with no memory corruption, gadget chain, or race involved. The prerequisites are specific: a front end that reuses FastCGI connections, and an application path that opens php://input without reading it to the end. WatchTowr's Jake Knott names the same bug among the three his firm expects attackers to go after first, alongside CVE-2026-115560 and CVE-2026-126714.
Three of the seven are cleanup from last month. Per Upwind, CVE-2026-129481 and CVE-2026-129182 cover cases the October fix for CVE-2026-109619 did not reach, and CVE-2026-129474 became remotely reachable because of a change introduced in 8.5.12. Version matters here. CVE-2026-129474 and CVE-2026-129182 apply only to PHP 8.5, and both depend on that version's fatal error backtrace engine. CVE-2026-129481 excludes 8.2 and exploits session cleanup behavior added in 8.3.
Knott's argument is that a critical rating does not tell you whether you are exposed. He offers three questions to narrow it down. How is PHP running: PHP-FPM, Apache mod_php, php-cgi, or something else? How are sessions configured, and is session upload progress enabled? What settings is PHP running with, and where are errors logged? Answering those rules out most of the list and leaves a prioritized set of assets to patch, in his words, "from a position of understanding and actual risk." He separates accelerated business-as-usual patching from the panic around trivially exploitable default-configuration bugs that earn a "product2shell" label, a category this release does not fall into.
Finding where PHP runs
The harder problem, per Arctic Wolf's Justin Moore, is knowing where PHP even runs. Many organizations lack a complete inventory, especially across legacy applications, internally built web services, managed hosting, and third-party software, where PHP is baked into CMS platforms, hosting control panels, and vendor appliances. Internet-facing PHP should move toward the front of the queue, he says, because attackers have repeatedly shown they move fast when a PHP vulnerability offers a path to code execution.
One item that is easy to miss: container images and appliances that bundle their own PHP build. Upwind flags them as needing a rebuild or a vendor update, not just a package upgrade on the host.
Top comments (0)