PHP: 2 flaws used in attacks; attackers can run their own code
OFFICIAL NAMES: RCE via stale global state · RCE via OOM corruption
WHAT IT IS · WEBSITE OR ONLINE STOREIt runs public websites, online stores or the software behind them.
DO THIS FIRSTAsk whoever runs your website or store to update it. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY 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.
WHY THIS VERDICT Attacks are confirmed. The vulnerability is 20 days old, so many systems are likely still unpatched. Ready-made attack tools are public. The severity score is critical (9.2). The exploit prediction score is 100%.
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. Ready-made attack tools are public. The confirmation is 16 days old.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- READY TO USE
How far has it climbed?
01 TALK
■ CONFIRMEDNEWEST EVIDENCE · 10 INDEPENDENT SOURCESCVE-2026-109619 discussed publicly (CIRCL sighting). CVE-2026-109618 discussed publicly (CIRCL sighting).
- SRC: CIRCL Vulnerability-Lookup sightings: CVE-2026-109619 discussed publicly (CIRCL sighting) · NOV 10
- SRC: CIRCL Vulnerability-Lookup sightings: CVE-2026-109618 discussed publicly (CIRCL sighting) · NOV 10
- SRC: The Register (security): Suspected Chinese attackers built a custom PHP2Shell exploit and rooted 25 servers · OCT 29
- SRC: The Register (security): CISA confirms PHP2Shell under attack as researchers clock successful exploits · OCT 27
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 3 INDEPENDENT SOURCESAttack attempts on CVE-2026-109619 seen by honeypots (Shadowserver via CIRCL). Attack attempts on CVE-2026-109619 seen by honeypots (Shadowserver via CIRCL).
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 3 INDEPENDENT SOURCESExploitation of CVE-2026-109619 reported (CIRCL sighting). Exploitation of CVE-2026-109618 reported (CIRCL sighting).
- SRC: CIRCL Vulnerability-Lookup sightings: Exploitation of CVE-2026-109619 reported (CIRCL sighting) · OCT 27
- SRC: CIRCL Vulnerability-Lookup sightings: Exploitation of CVE-2026-109618 reported (CIRCL sighting) · OCT 27
- SRC: CISA Known Exploited Vulnerabilities: PHP Stale Internal Request-State Vulnerability · OCT 25
- SRC: CISA Known Exploited Vulnerabilities: PHP Memory Corruption Vulnerability · OCT 25
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLIC
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Oct 29, 2026, has passed. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run PHP? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- OCT 17, 2026619 public GitHub repositories claim a proof of concept for CVE-2026-109618
- OCT 21, 2026Critical security issue affecting PHP
- OCT 21, 2026PHP releases emergency fixes for 2 critical vulnerabilities
- Attack activity. OCT 21, 2026CISA Vulnrichment marks CVE-2026-109618 as actively exploited
- Attack activity. OCT 21, 2026CISA Vulnrichment marks CVE-2026-109619 as actively exploited
- OCT 21, 202623 public GitHub repositories claim a proof of concept for CVE-2026-109619
- OCT 21, 2026PHP devs publish critical bug fix as site owners warned: Pull 'em offline if you're unpatched
- OCT 21, 2026Widespread PHP Flaw May Cause Many Site Outages Today
- OCT 21, 2026Critical PHP Vulnerability (CVE-2026-109618, CVE-2026-109619) [infocon yellow], (Wed, Oct 21st)
- Attack activity. OCT 21, 2026Exploitation of CVE-2026-109619 reported (CIRCL sighting) (7 reports, latest OCT 27)
- Attack activity. OCT 21, 2026Exploitation of CVE-2026-109618 reported (CIRCL sighting) (8 reports, latest OCT 27)
- OCT 21, 2026PHP blames supply chain security biz Chainguard for putting huge chunks of the web at risk
SOURCES
- [1] nuclei-templates: Nuclei scan template: PHP2Shell (CVE-2026-109618/CVE-2026-109619) - Active Crash Detection, OCT 24
- [2] nuclei-templates: Nuclei scan template: PHP 8.2 < 8.2.35, 8.3 < 8.3.36, 8.4 < 8.4.27, 8.5 < 8.5.12 - Use-After-Free Remote Code Execution, NOV 3
- [3] CIRCL Vulnerability-Lookup sightings: CVE-2026-109619 discussed publicly (CIRCL sighting), NOV 10
- [4] CIRCL Vulnerability-Lookup sightings: Public proof of concept for CVE-2026-109618 (CIRCL sighting), NOV 10
- [5] CIRCL Vulnerability-Lookup sightings: Public proof of concept for CVE-2026-109619 (CIRCL sighting), NOV 10
- [6] The Register (security): Suspected Chinese attackers built a custom PHP2Shell exploit and rooted 25 servers, OCT 29
- [7] The Register (security): CISA confirms PHP2Shell under attack as researchers clock successful exploits, OCT 27
- [8] Canadian Centre for Cyber Security: PHP security advisory (AV26-1070) - Update 1, OCT 27
- [9] Security Affairs: U.S. CISA adds PHP flaws PHP2Shell to its Known Exploited Vulnerabilities catalog, OCT 27
- [10] The Hacker News: CISA Confirms Active Exploitation of Two PHP2Shell Flaws Enabling Remote Code Execution, OCT 26
- [11] Security Affairs: PHP2Shell: Suspected North Korean campaign targets 216 vulnerable PHP hosts, OCT 26
- [12] BleepingComputer: PHP2Shell security flaws now sucessfully exploited in the wild, OCT 26
- [13] The Register (security): PHP2Shell: No login, no app code, no warning. What next?, OCT 26
- [14] CISA Known Exploited Vulnerabilities: PHP Stale Internal Request-State Vulnerability, OCT 25
- [15] CISA Known Exploited Vulnerabilities: PHP Memory Corruption Vulnerability, OCT 25
- [16] The Hacker News: PHP2Shell Exploitation Hits Government Entity Amid Global Scanning and Signs of AI-Assisted Hacking, OCT 25
- [17] Security Affairs: PHP Warns of New Code Execution Flaw Days After PHP2Shell Patches, OCT 23
- [18] Canadian Centre for Cyber Security: AL26-026 - Critical vulnerabilities impacting PHP - CVE-2026-109618 and CVE-2026-109619 - Update 1, OCT 23
- [19] The Hacker News: PHP2Shell Exploit Attempts Hit Millions as Attackers Try to Deploy Mirai Malware, OCT 23
- [20] Exploit-DB: Exploit-DB entry: PHP2Shell (CVE-2026-109618) - PHP core versions after v5.4 - RCE, OCT 21
- [21] SANS Internet Storm Center: Critical PHP Vulnerability (CVE-2026-109618, CVE-2026-109619) [infocon yellow], (Wed, Oct 21st), OCT 21
- [22] Krebs on Security: Widespread PHP Flaw May Cause Many Site Outages Today, OCT 21
- [23] PoC-in-GitHub: 23 public GitHub repositories claim a proof of concept for CVE-2026-109619, OCT 21
- [24] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-109619 as actively exploited, OCT 21
- [25] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-109618 as actively exploited, OCT 21
- [26] CyberScoop: PHP releases emergency fixes for 2 critical vulnerabilities, OCT 21
- [27] UK NCSC: Critical security issue affecting PHP, OCT 21
- [28] PoC-in-GitHub: 619 public GitHub repositories claim a proof of concept for CVE-2026-109618, OCT 17
- [29] CIRCL Vulnerability-Lookup sightings: 649 more reports
- [30] The Register (security): 6 more reports
- [31] Security Affairs: 1 more reports