CVE-2026-109618
🔴 High In CISA KEVPHP — every installation that serves web requests: PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed. PHP rates the risk highest for Apache mod_php, where an attack can land before the application's own code runs, and states that no configuration change fully mitigates. Siemens has since declared RUGGEDCOM APE1808 affected (all versions, SSA-566512), which pulls this into OT estates · 8.2.* < 8.2.35 ; 8.3.* < 8.3.36 ; 8.4.* < 8.4.27 ; 8.5.* < 8.5.12 — but the structured record understates the scope: 8.1, 8.0 and 7.4 are affected in all versions with no official release (PHP published minimal source backports; use distribution or LTS packages), and 7.3 and older including PHP 5 are affected with no fix at all (watchTowr confirmed PHP 5; researchers put it back to 5.4)
100.00th percentile
due 2026-10-29
Exploitation
kev block, and its CISA-ADP SSVC still reads exploitation none / automatable no / impact total with a timestamp of 21/10/2026, even though the ADP container was republished on 27/10/2026 at 03:55 UTC. The KEV listing therefore rests on secondary reporting (Tenable, securityonline) because the CISA catalogue and the 26/10 alert would not load ; the record's "none" is demonstrably stale and should not be cited. Exploitation: confirmed in honeypots and labs, not yet in a named production victim. Adel Karimi (Perplexity) reported 35 shells across three honeypots on PHP 8.4.26 with Apache mod_php on 24/10/2026, confirming code execution with usable memory disclosure on a favourable single-worker profile, corroborated by Marcus Hutchins (Expel) ; Trail of Bits reported working exploits against pre-patch 8.2 to 8.5 with demonstrations on MediaWiki, Symfony, Laravel and phpBB ; CYFIRMA stated on 24/10/2026 that there was "no confirmed mass successful exploitation by this actor". Start your log review at 17/10/2026, not 21/10: Amazon MadPot recorded the first attempt on 17/10, four days before the honeypot wave. Fastly measured roughly 250,000 requests from about 3,200 IPs across 21-22/10. IOCs (hunt.io, 22/10/2026): scanner network 45.198.224.0/24 (AS215925) ; payload host 92.118.112.100 ; operator hosts including 206.188.197.105, 104.219.251.31 and 58.221.60.160 ; C2 wildcard domains including .botlesscucks[.]st ; web shells shell.php and autologin_fd.php plus tebaran_ deployers ; user agents such as php2shell-scan/109618 ; one JA4H hash ; no file hashes. CYFIRMA adds hxxp://92.118.112[.]100/nfs and hashes for an "nfs" ELF, single-vendor and uncorroborated. Attribution: suspected only. CYFIRMA assesses a Korean-speaking operator in the Lazarus ecosystem, high confidence on a DPRK nexus but only moderate on Lazarus itself, from 21 scan nodes against a 216-host target set. No named malware family ; the second stage is described only as a Mirai-style loader. Patch adoption: Brandefense Atlas found 59% of 3,532 version-readable sites still pre-fix over 21-25/10, with the patched share of first daily checks rising from 21% to 50% across those days — a self-selected sample using header-only detection CERT Santé (21/10/2026, updated 23/10) independently marks this actively exploited and dates the first attempts to 17/10/2026, corroborating the Amazon MadPot figure, and states a proof of concept is available in open sources Update 29/10/2026: the kev block has now appeared in the record, dateAdded 26/10/2026, and the SSVC options have flipped to exploitation active — though the SSVC timestamp still reads 21/10, so the ADP container's own dateUpdated is the only reliable signal that it moved. Today is the federal remediation deadline. The compromise picture is contested and has in part gone backwards: Palo Alto's Unit 42 withdrew its European government agency intrusion claim and Sophos withdrew its compromise report, and CISA has named no victim. Against that, one vendor reports a php2shell to CVE-2026-46300 ("Fragnesia") chain rooting 25 servers across the US, Japan, Taiwan and South Korea, three in a US government-affiliated environment, observed 25/10/2026 — that is the first credible production-compromise claim, from a single source, and the privilege escalation half is a separate KEV-listed kernel bug. A Mirai-derived payload named Potassium is now associated with the activity by two vendors, but both state the payload was not delivered or run. No corroboration of the earlier suspected-DPRK attribution. Patch adoption: 2,071 of 3,532 version-readable sites were still pre-fix (59%), one tracker puts exposed vulnerable machines down about 67% and affected organisations down about 48%, with under 53% still vulnerable a week after disclosure ; TU Delft counted 72,343 exploitation requests from 171 IPs Update 30/10/2026: still no named production victim. Palo Alto confirms active exploitation against internet-exposed PAN-OS management interfaces and is contacting affected customers individually, but names none. Unit 42's retraction stands and was not revisited: its 23/10 agentic-AI post-exploitation detail was retracted on 25/10 with the statement that it was "unable to confirm that initial access is associated with the specific PHP2Shell CVEs", and its 29/10 update does not reopen it. Unit 42 names no malware at all, so the Mirai-derived "Potassium" association remains two other vendors' and remains undelivered on their own account. No CISA statement after the 29/10 deadline was found, which is partly an artefact of the catalogue being unreachable. Existing PoC (not opened), recorded from the proof-of-concept list supplied on 09/11/2026. Its sibling CVE-2026-109619 is in the same list. Update 13/11/2026 — production compromise now confirmed: the line above saying exploitation was "not yet in a named production victim" is superseded. Check Point (CPR, 12/11/2026, sk1000362) reports PHP2Shell used against unpatched Check Point Mobile Access portals from 30/10/2026 (Israeli organisations, followed by root through CVE-2026-123039 and a wiper on VMware ESXi) and a second wave from 02/11/2026, with "a couple of dozen" customers compromised and activity until 04/11/2026. Most recent dated exploitation: 04/11/2026, 9 days old, inside the 60-day window, so 🔴 standsTimeline
- 21/10/2026PHP discloses two critical RCE flaws, emergency release due today
- 21/10/2026CVE record published (CVE List)
- 22/10/2026PHP ships emergency fix for two critical pre-auth RCE flaws
- 23/10/2026PHP2Shell update — mass exploitation attempts, still no confirmed compromise
- 26/10/2026PHP2Shell (CVE-2026-109618 / CVE-2026-109619) update
- 26/10/2026PHP2Shell exploitation escalates to a confirmed government breach
- 26/10/2026Added to the CISA KEV catalogue
- 27/10/2026PHP2Shell flaws now confirmed actively exploited, added to CISA KEV
- 27/10/2026Suspected North Korea-linked scanning wave against PHP2Shell flaws
- 29/10/2026PHP2Shell exploitation expands — Fragnesia kernel flaw chained to root firewalls, PAN-OS also targeted
- 29/10/2026CISA deadline for US federal agencies
- 30/10/2026PAN-OS "PHP2Shell" chain exploited by China-nexus actor to root 25 servers
- 30/10/2026Suspected China-nexus actor roots 25 PAN-OS servers
- 13/11/2026PHP2Shell used to break into Check Point gateways, then root and wipe ESXi hosts
- 16/11/2026Check Point Gaia root flaw: CISA deadline is today, and a stopgap exists
- 17/11/2026Trend Micro Apex One: 18 agent flaws fixed, plus a PHP update against PHP2Shell
- 19/11/2026PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13 fix seven Critical flaws, including the session-handler RCE
Relationships
exploits suspected named in the same story vendor · Select a box to open its page · All relationships
Risk
longjmp() while some contexts leave request memory uninitialised before an allocation, so the request-cleanup path reads or branches on that memory. A multipart request with no usable size bypasses post_max_size and triggers the exhaustion, and the attack lands before the application's own code runs)Fix
memory_limit=-1 as a non-modifiable php_admin_value ; cap post_max_size (8M, or 32M where file uploads are used) ; cap the request size at the web server or proxy ; cap multipart parts, headers and uploads, or block multipart requests outright where the application does not use them ; do not use RLIMIT_AS or RLIMIT_DATA. On PHP 8.5 also set fatal_error_backtraces=0 and restart workers. For end-of-life branches, session.upload_progress.enabled = Off in php.ini plus a service restart. Hunt for PHP worker processes (php-fpm, php-cgi, httpd, apache2) spawning shells, interpreters or network toolsOfficial description
PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CWE-1325,CWE-1419,CWE-416,CWE-755,CWE-824