CVE-2026-109618
PHP Memory Corruption Vulnerability
Description
CVE-2026-109618 is a critical memory-safety vulnerability in the PHP interpreter that allows unauthenticated attackers to achieve remote code execution by deliberately triggering out-of-memory (OOM) conditions. PHP aborts a request on an OOM error via longjmp(), and some code paths leave request memory uninitialized before an allocation, so the subsequent cleanup reads or branches on that memory, a pattern that combines improper handling of exceptional conditions with access of uninitialized pointers and use after free. PHP 7.3.0 up to the fixed releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12 is affected, as are products that embed PHP such as Palo Alto Networks PAN-OS, Panorama virtual appliances and Siemens RUGGEDCOM APE1808 firmware. CISA lists CVE-2026-109618 in its Known Exploited Vulnerabilities (KEV) catalog, and an EPSS score of 99.999% makes this PHP vulnerability one of the most likely to be exploited of all tracked CVEs.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorCWEs
Affected Products
| Vendor | Product | Version |
|---|---|---|
| php | php | >= 7.3.0, < 8.2.35; >= 8.3.0, < 8.3.36; >= 8.4.0, < 8.4.27; >= 8.5.0, < 8.5.12 |
| siemens | ruggedcom ape1808 firmware | - |
| paloaltonetworks | pan-os | >= 10.2.0, < 10.2.7; 10.2.7; 10.2.8; 10.2.9; 10.2.10; 10.2.11; 10.2.12; 10.2.13; 10.2.14; 10.2.15; 10.2.16; 10.2.17; 10.2.18; >= 11.1.0, < 11.1.4; 11.1.4; 11.1.5; 11.1.6; 11.1.7; 11.1.8; 11.1.9; 11.1.10; 11.1.11; 11.1.12; 11.1.13; 11.1.14; 11.1.15; 11.1.16; >= 11.2.0, < 11.2.4; 11.2.4; 11.2.5; 11.2.6; 11.2.7; 11.2.8; 11.2.9; 11.2.10; 11.2.11; 11.2.12; 11.2.13; 11.2.15; 11.2.16; >= 12.1.0, < 12.1.4; 12.1.4; 12.1.5; 12.1.6; 12.1.7; 12.1.8; 12.1.9; 12.1.10; >= 12.2.0, < 12.2.4; 12.2.4; - |
| paloaltonetworks | panorama virtual appliance | - |
| siemens | blueplanet 360 nx3 m6 wm od iisx firmware | - |
| siemens | blueplanet 360 nx3 m6 wm od iisx-s firmware | - |
| siemens | energy engage | 2.0; 3.1 |
| siemens | local monitoring bt-monitoring-vm | < 20261103 |
| siemens | spectrum power 4 | - |
| siemens | spectrum power 7 | - |
| siemens | spectrum power tg | - |
| siemens | amis ts | - |
References
- https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w(Mitigation, Vendor Advisory)
- http://seclists.org/fulldisclosure/2026/Oct/51(Mailing List)
- http://www.openwall.com/lists/oss-security/2026/10/21/6(Mailing List, Third Party Advisory)
- http://www.openwall.com/lists/oss-security/2026/10/23/5(Mailing List, Third Party Advisory)
- https://github.com/rapid7/metasploit-framework/pull/22139(Third Party Advisory)
- https://arcticwolf.com/resources/blog/php2shell-critical-php-vulnerabilities-enable-unauthenticated-remote-code-execution/(Third Party Advisory)
- https://cert-portal.siemens.com/productcert/html/ssa-166980.html(Third Party Advisory)
- https://cert-portal.siemens.com/productcert/html/ssa-566435.html(Third Party Advisory)
- https://cert-portal.siemens.com/productcert/html/ssa-566512.html(Third Party Advisory)
- https://php2shell.delftintellab.com/(Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-109618(US Government Resource)
- https://www.wiz.io/blog/php2shell-php-rce(Third Party Advisory)
Weakness Type
CWE-416: Use After Free
Use after free occurs when software keeps using memory after it has been released. In CVE-2026-109618, the request cleanup routine operates on request memory whose state was not properly established after an aborted allocation, which can let an attacker influence what the interpreter reads and executes.
Learn more: CWE-416 — Use After Free
CWE-755: Improper Handling of Exceptional Conditions
This weakness describes software that detects an exceptional condition but responds to it inadequately. PHP detects the OOM error and jumps out of the current context via longjmp(), but some contexts do not account for this abort and leave memory in an inconsistent state.
Learn more: CWE-755 — Improper Handling of Exceptional Conditions
CWE-824: Access of Uninitialized Pointer
Accessing an uninitialized pointer means dereferencing a value that was never set to a valid address. Here, request memory remains uninitialized before an allocation, and the cleanup procedure later reads or branches on it, which can redirect program flow.
Learn more: CWE-824 — Access of Uninitialized Pointer
CWE-1325: Improperly Controlled Sequential Memory Allocation
This weakness covers repeated allocations whose combined memory use is not properly bounded. Attackers can use this to drive PHP into the OOM condition on demand, which is the trigger for the vulnerable error path in CVE-2026-109618.
Learn more: CWE-1325 — Improperly Controlled Sequential Memory Allocation
Impact Analysis
CVE-2026-109618 carries a CVSS v3.1 base score of 9.8 (Critical). The vulnerability is remotely exploitable over the network, easy to exploit with no special conditions needed, requires no authentication and no user action. A successful attack results in remote code execution in the context of the PHP process, putting Confidentiality (High) of application data, credentials and secrets, Integrity (High) of code and stored data, and Availability (High) of the web service at risk. Because PHP is embedded in network appliances such as Palo Alto Networks PAN-OS and Panorama as well as Siemens RUGGEDCOM APE1808 firmware, the exposure reaches beyond classic web servers into security and industrial infrastructure. With an EPSS score of 99.999%, the likelihood of active exploitation is extremely high.
Exploit Maturity
CISA has added CVE-2026-109618 to its Known Exploited Vulnerabilities catalog, which confirms active exploitation in the wild; ransomware use is currently listed as unknown. The EPSS score of 99.999% (99.998th percentile) indicates near-certain exploitation activity. The vulnerability has been publicly documented by third parties under the name "PHP2Shell", including an analysis by Arctic Wolf and a dedicated research page, and the description states that multiple OOM strategies can consistently trigger the condition.
Remediation
- Follow the CISA KEV directive: "Apply mitigations in accordance with vendor instructions [...] or discontinue use of the product if mitigations are unavailable." The KEV due date of 2026-10-29 has already passed.
- Upgrade PHP: Update to PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or later, depending on your branch. All versions from 7.3.0 onward below these releases are affected; end-of-life branches older than 8.2 should be migrated to a supported release. Consult the PHP security advisory GHSA-w8hw-w9fx-j79w for mitigation details.
- Patch embedded products: Apply vendor fixes for Palo Alto Networks PAN-OS (10.2, 11.1, 11.2, 12.1, 12.2 branches) and Panorama virtual appliances, and follow Siemens advisories SSA-166980, SSA-566435 and SSA-566512 for RUGGEDCOM APE1808.
- Reduce exposure in the interim: Restrict access to PHP applications and appliance management interfaces to trusted networks, place them behind a WAF or reverse proxy that limits request body sizes and upload volumes, and enforce aggregate memory limits at the system level to contain memory exhaustion attempts.
- Monitor and investigate: Review logs for bursts of PHP "Allowed memory size exhausted" errors, crashing worker processes, unusual child processes spawned by PHP-FPM or the web server, and new web shells. Because the flaw is actively exploited, perform forensic triage on internet-facing hosts that ran vulnerable versions.
Technical Details
PHP handles out-of-memory errors by calling longjmp() to leave the current execution context and abort the request, an exception path that not every internal context accounts for (CWE-755). In the affected code, request memory is left uninitialized before an allocation fails, and the request cleanup procedure later reads or branches on this memory (CWE-824), effectively operating on memory whose lifecycle is no longer valid (CWE-416). Because memory consumption per request can be steered by attacker input (CWE-1325), an attacker can reliably force the OOM condition and position controlled data in the affected memory region, turning the cleanup into a code execution primitive. The CVSS vector AV:N/AC:L/PR:N/UI:N reflects that an unauthenticated attacker with network access to a PHP application can exploit the flaw, and the description notes that multiple OOM strategies trigger the condition consistently.
Frequently Asked Questions
Is CVE-2026-109618 being actively exploited?
Yes. CISA lists CVE-2026-109618 in its Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, and the EPSS score of 99.999% indicates near-certain exploitation activity. Ransomware use is currently listed as unknown.
What products are affected by CVE-2026-109618?
PHP from version 7.3.0 up to, but not including, 8.2.35, 8.3.36, 8.4.27 and 8.5.12 is affected. Products embedding PHP are also listed, including Palo Alto Networks PAN-OS (10.2, 11.1, 11.2, 12.1 and 12.2 branches), Panorama virtual appliances and Siemens RUGGEDCOM APE1808 firmware.
How do I fix CVE-2026-109618?
Upgrade PHP to 8.2.35, 8.3.36, 8.4.27 or 8.5.12 or later and apply the vendor updates for PAN-OS, Panorama and RUGGEDCOM APE1808. Until patched, restrict network access to affected systems and check internet-facing hosts for signs of compromise.
How severe is CVE-2026-109618?
CVE-2026-109618 is rated Critical with a CVSS v3.1 score of 9.8, because unauthenticated remote attackers can execute code with low attack complexity. Its EPSS score of 99.999% places it in the 99.998th percentile of all scored vulnerabilities.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.