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 cle
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. Multiple OOM strategies can consistently trigger this condition and…
| Vendor | Product | Versions |
|---|---|---|
| php | php | >= 7.3.0, < 8.2.35 |
| php | php | >= 8.3.0, < 8.3.36 |
| php | php | >= 8.4.0, < 8.4.27 |
| php | php | >= 8.5.0, < 8.5.12 |
| siemens | ruggedcom_ape1808_firmware | unspecified |
| paloaltonetworks | pan | os — >= 10.2.0, < 10.2.7 |
| paloaltonetworks | pan | os — 10.2.7 |
| paloaltonetworks | pan | os — 10.2.8 |
| paloaltonetworks | pan | os — 10.2.9 |
| paloaltonetworks | pan | os — 10.2.10 |
| paloaltonetworks | pan | os — 10.2.11 |
| paloaltonetworks | pan | os — 10.2.12 |
| paloaltonetworks | pan | os — 10.2.13 |
| paloaltonetworks | pan | os — 10.2.14 |
| paloaltonetworks | pan | os — 10.2.15 |
| paloaltonetworks | pan | os — 10.2.16 |
| paloaltonetworks | pan | os — 10.2.17 |
| paloaltonetworks | pan | os — 10.2.18 |
| paloaltonetworks | pan | os — >= 11.1.0, < 11.1.4 |
| paloaltonetworks | pan | os — 11.1.4 |
| paloaltonetworks | pan | os — 11.1.5 |
| paloaltonetworks | pan | os — 11.1.6 |
| paloaltonetworks | pan | os — 11.1.7 |
| paloaltonetworks | pan | os — 11.1.8 |
| paloaltonetworks | pan | os — 11.1.9 |
| paloaltonetworks | pan | os — 11.1.10 |
| paloaltonetworks | pan | os — 11.1.11 |
| paloaltonetworks | pan | os — 11.1.12 |
| paloaltonetworks | pan | os — 11.1.13 |
| paloaltonetworks | pan | os — 11.1.14 |
| paloaltonetworks | pan | os — 11.1.15 |
| paloaltonetworks | pan | os — 11.1.16 |
| paloaltonetworks | pan | os — >= 11.2.0, < 11.2.4 |
| paloaltonetworks | pan | os — 11.2.4 |
| paloaltonetworks | pan | os — 11.2.5 |
| paloaltonetworks | pan | os — 11.2.6 |
| paloaltonetworks | pan | os — 11.2.7 |
| paloaltonetworks | pan | os — 11.2.8 |
| paloaltonetworks | pan | os — 11.2.9 |
| paloaltonetworks | pan | os — 11.2.10 |
| paloaltonetworks | pan | os — 11.2.11 |
| paloaltonetworks | pan | os — 11.2.12 |
| paloaltonetworks | pan | os — 11.2.13 |
| paloaltonetworks | pan | os — 11.2.15 |
| paloaltonetworks | pan | os — 11.2.16 |
| paloaltonetworks | pan | os — >= 12.1.0, < 12.1.4 |
| paloaltonetworks | pan | os — 12.1.4 |
| paloaltonetworks | pan | os — 12.1.5 |
| paloaltonetworks | pan | os — 12.1.6 |
| paloaltonetworks | pan | os — 12.1.7 |
Yes — actively exploited. Added to the CISA KEV catalog on 2026-10-26. Ransomware use: Unknown.
For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.
Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.
No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.