Palo Alto Networks PHP is affected by a critical memory corruption flaw, CVE-2026-109618, that can lead to remote code execution. CISA lists it as exploited.
What is affected
The public sources name the product as Palo Alto Networks PHP and describe the issue as a memory corruption vulnerability, tracked as CVE-2026-109618. It was disclosed on 2026-10-21. The sources give these affected version ranges:
≥ 10.2.0, < 10.2.7≥ 11.1.0, < 11.1.4≥ 11.2.0, < 11.2.4≥ 12.1.0, < 12.1.4≥ 12.2.0, < 12.2.4
A range such as < 10.2.7 means the versions before 10.2.7. The vendor advisory lists the fixed releases and explains how to check whether you are exposed. You can read it in the PHP security advisory on GitHub.
What the flaw allows
According to the sources, PHP handles out-of-memory errors by leaving the current context and aborting the request. Some contexts do not account for this properly and leave request memory uninitialised before an allocation is made. The cleanup step that follows may then read or branch on that memory. The description states that several out-of-memory strategies can trigger this condition consistently and lead to remote code execution.
The sources list the weakness types CWE-416, CWE-755, CWE-824, CWE-1325 and CWE-1419. The CVSS 3.1 base score is 9.8, which is critical. The vector indicates that the flaw can be reached over the network with low complexity, without privileges and without user interaction, with high impact on confidentiality, integrity and availability. Details are on the NVD entry.
Exploitation
CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-10-26. CISA states a due date of 2026-10-29, which is its deadline for US federal agencies. CISA lists known ransomware use as unknown. CISA has also published an alert on critical PHP vulnerabilities, and the entry can be found in the CISA catalogue.
What to do
Check whether you run Palo Alto Networks PHP in any of the version ranges above, including systems that are reachable from the internet. Then follow the vendor advisory for the fixed releases and any mitigations. This advisory summarises public sources only. Pinet has not analysed or tested the vulnerability.
What to do
Follow the instructions in the PHP security advisory on GitHub, which lists the fixed releases. CISA's required action is to apply mitigations in line with the vendor instructions, or to stop using the product if mitigations are not available. Review which of your systems are exposed to the internet first.
Sources
- https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w
- https://www.php.net/
- https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching
- https://nvd.nist.gov/vuln/detail/CVE-2026-109618
- http://www.openwall.com/lists/oss-security/2026/10/21/6
- http://www.openwall.com/lists/oss-security/2026/10/23/5
- https://arcticwolf.com/resources/blog/php2shell-critical-php-vulnerabilities-enable-unauthenticated-remote-code-execution/
- https://cert-portal.siemens.com/productcert/html/ssa-566512.html
- https://php2shell.delftintellab.com
- https://www.wiz.io/blog/php2shell-php-rce
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog