Palo Alto Networks reports that PHP can keep stale internal request state after the memory behind it is freed, which can lead to remote code execution. CISA lists CVE-2026-109619 as exploited.
What is affected
The sources describe CVE-2026-109619 as a flaw in Palo Alto Networks PHP. The sources give the following 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
The flaw was disclosed on 2026-10-21. The vendor advisory lists the fixed releases and is the place to confirm whether a specific installation falls inside these ranges. You can read it in the PHP security advisory on GitHub.
What the flaw allows
According to the description in the sources, PHP keeps various global state that temporarily points into request memory. In some scenarios this state is not correctly reset, or it is filled in again after it has been reset. It can then refer to request memory even after that memory has been freed. Later requests may read or branch on this stale state before it is fully initialised.
The sources state that several strategies can trigger this condition and produce remote code execution. The NVD entry lists a CVSS 3.1 base score of 8.1, which is a high severity rating, with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. That vector describes an attack over the network that needs no privileges and no user interaction, but has high attack complexity. The sources list the weakness identifiers CWE-416, CWE-755, CWE-824, CWE-1325 and CWE-1419. More detail is in the NVD entry for CVE-2026-109619.
Exploitation
CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-10-26. CISA's stated deadline for US federal agencies to act is 2026-10-29. CISA records its knowledge of use in ransomware campaigns as unknown. The entry is part of the CISA Known Exploited Vulnerabilities catalogue, and CISA has also published an alert on PHP vulnerabilities.
Pinet has not analysed or tested this vulnerability. This advisory summarises what the public sources report.
What to do
Check whether any system you run uses a version inside the affected ranges above, and follow the vendor advisory for the fixed releases and for the steps to confirm exposure. CISA's required action is to apply mitigations in accordance with vendor instructions. The detailed steps are in the mitigation section of this advisory.
What to do
Follow the vendor instructions in the PHP security advisory on GitHub, which lists the fixed releases and how to check exposure.
CISA's required action for this entry is to apply mitigations in accordance with vendor instructions and to discontinue use of the product if mitigations are unavailable. The sources do not describe any other workaround. Prioritise systems that are reachable from the internet, because the flaw is described as remotely exploitable.
Sources
- https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp
- 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-109619
- http://www.openwall.com/lists/oss-security/2026/10/21/16
- http://www.openwall.com/lists/oss-security/2026/10/21/17
- http://www.openwall.com/lists/oss-security/2026/10/21/23
- http://www.openwall.com/lists/oss-security/2026/10/21/7
- http://www.openwall.com/lists/oss-security/2026/10/22/14
- http://www.openwall.com/lists/oss-security/2026/10/22/15
- http://www.openwall.com/lists/oss-security/2026/10/22/16
- http://www.openwall.com/lists/oss-security/2026/10/22/19
- http://www.openwall.com/lists/oss-security/2026/10/22/2
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog