PHP insecure error handling and state management
PHP insecurely handles multiple combinations of memory allocations and error conditions. These behaviors can allow a remote attacker to cause a denial of service or execute arbitrary code. Successful exploitation depends on a number of factors including the specific PHP application being targeted, the SAPI and web server, error handling and memory resource configuration, and platform or OS-level memory protections. Without significant analysis effort to prove otherwise, any application running on a vulnerable version of PHP should be considered vulnerable and exploitable.
describes (2)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-109619US | high8.1 | Exploit | ||
PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The g… | ||||
| CVE-2026-109618US | critical9.8 | Exploit | ||
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… | ||||
references
External citations — patches, advisories, analysis.
remediations (2)
- Fixedphp-src
Fixed in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12.
https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w - Fixedphp-src
Fixed in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12.
https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan