Key facts
- PHP rated each PHP2Shell vulnerability 9.2 under CVSS v4.0.
- The PHP security team said updating is the only safe choice and no configuration change fully substitutes for updating.
- PHP maintainers issued an advisory on Wednesday warning of an upcoming security release addressing critical flaws affecting all supported PHP versions.
- PHP describes the release as part of its regular four-week release cycle.
PHP maintainers warned on Wednesday of critical flaws affecting every supported PHP version and scheduled a security release for November 19, 2026, between 2:00 p.m. and 2:30 p.m. UTC.
The release follows PHP’s regular four-week cycle and carries a CRITICAL severity rating. The maintainers said critically rated issues depend on either non-default configuration or uncommon setups, and they withheld technical specifics ahead of the fix.
PHP expects the fix due out to contain CVE-2026-115560, a remote code execution vulnerability that lets attackers run code on a server. Exploiting it requires session.serialize_handler set to php_binary or php_serialize and changed to php using ini_set() before session_start(). PHP enables session upload progress by default.
Before the fix is available, the project advised users to disable session.upload_progress.enabled by setting it to 0 until the next scheduled bug fix release lands. It takes effect after the PHP worker restarts and remains in place until the next regular bug fix release. Everyone using PHP should install the patches immediately upon release.
IT staff should inventory every place PHP runs, including web servers, containers, CI images and development machines, and record the version on each. Administrators should identify who applies PHP updates and, on managed or shared hosting, ask the provider when it plans to deploy.
On their own servers, administrators should plan a maintenance window shortly after 14:00 UTC on patch day. They should check for unsupported PHP versions because security fixes normally cover only supported branches, currently PHP 8.2 through 8.5, and sites on older versions may need a branch upgrade.
For WordPress sites, administrators can find the PHP version under Tools, Site Health, Info, Server. Before the specifics are released, system operators should treat all PHP installations they manage as potentially vulnerable. The PHP team may release earlier than planned if details become public or if it finds attackers exploiting the flaws.
About a month before the November advisory, PHP issued fixes for two critical flaws grouped as PHP2Shell, tracked as CVE-2026-109618 and CVE-2026-109619. PHP2Shell enables unauthenticated remote code execution through specially crafted HTTP requests.
The PHP security team scheduled emergency updates for October 21, 2026, at 14:00 UTC to fix CVE-2026-109618 and CVE-2026-109619. PHP released patched versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21, 2026.
Volker Dusch, PHP release manager, said, “After many weeks of work, I’m very glad we got the release out.” The disclosure moved up by a day to October 21 because details leaked in a Hacker News post.
Attackers have used the PHP2Shell flaws in limited active exploitation against publicly accessible Palo Alto Networks management interfaces and Check Point Security Gateways, targeting Active Directory and delivering backdoors. A Hunt.io report from October 30, 2026 counted 616 PHP2Shell-related files across multiple hosts, including exploit kits, cloned proof-of-concepts, custom heap exploits, scanners and post-exploitation tooling. Underground forum participants have sought PHP2Shell exploits, discussed prerequisites and debated whether circulating proof-of-concepts worked.
CrowdStrike said a single exploit that works reliably across every affected PHP setup is unlikely to exist. watchTowr said it believes it reproduced CVE-2026-109618 but held back technical details until patches arrived, and said it has not seen PHP2Shell exploitation in the wild even though information leaked. “In the last hour, two remote code execution vulnerabilities in PHP have been leaked,” Benjamin Harris of watchTowr said.
Calif discovered the first PHP2Shell flaw in August 2026 using OpenAI’s GPT-5.6 Sol model during an audit paid for by OpenAI’s Patch the Planet initiative. Wiz, which is part of Google, said its researchers found the issues separately weeks later using Wiz Atlas, Gemini 4 Argon and GPT-5.6 Sol. PHP’s advisory credits researchers from Calif, Wiz and OpenAI together.
Wiz estimates PHP runs roughly 70 percent of all websites. Cloudflare turned on WAF rules for all customers, including free accounts, at 03:02 UTC on October 21, roughly nine hours before disclosure.
PHP runs on network devices from pfSense, OPNsense, QNAP NAS, DrayTek, ZyXEL, D-Link, TP-Link, Netgear, Tenda and Synology, and on security appliances from Citrix, Palo Alto and Ivanti as well as F5 BIGIP load balancers. PHP said every PHP version since PHP 5 is affected, and PHP 5 reached end of life 21 years ago. PHP published backported fixes for the unsupported 7.4, 8.0 and 8.1 branches. Apache mod_php, PHP via FPM and LSAPI are vulnerable to the PHP2Shell flaws; Windows PHP servers are definitely vulnerable, while the effect on FrankenPHP is unclear.
The PHP security team said updating is the only safe choice and that no configuration change fully substitutes for updating. It suggested memory_limit=-1 as a temporary measure, post_max_size below one-quarter of the memory limit or 8M as a fallback, max_input_nesting_level around 8, and session.upload-progress.enabled=0. The team warned these measures can harm speed or functionality and are no substitute for promptly installing an update.
watchTowr claimed the flaws rate CVSS 10 and affect PHP versions 5 through 8, which conflicts with PHP’s official rating. PHP rated each PHP2Shell vulnerability 9.2 under CVSS v4.0.
CERT-EU, the UK NCSC, the US NSA, ENISA and Europol’s European Cybercrime Centre all issued alerts or advice on the PHP2Shell flaws. ENISA, CERT-EU and Europol’s EC3 advised organizations to locate vulnerable systems and install official updates, and the UK NCSC said exposed systems should take priority and temporary shutdowns might be worth considering. The Australian Cyber Security Centre and Canada’s Centre for Cyber Security also issued warnings on the PHP2Shell vulnerabilities. SlowMist warned cryptocurrency exchanges, DeFi platforms and wallet providers to urgently review PHP infrastructure after the October flaws.
Last month, PHP patched a critical Brotli flaw tracked as CVE-2026-111497, also called Node2Shell or Broccoli2Shell. CVE-2026-111497 is an out-of-bounds write in the Brotli decoder library that could lead to arbitrary code execution.
Patches for the November 19 flaws are due between 2:00 p.m. and 2:30 p.m. UTC on November 19, 2026. Administrators should stage for that window, treat the four-week release cycle as the fallback if it slips, and install updates immediately once released.

Join the discussion