PHP Group · PHP · PHP Memory Corruption Vulnerability
Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 1% of CVEs by near-term exploitation probability
Added to CISA KEV 2026-10-26 · exploited in the wild for 12 days
How a test catches it
Rarely a test finding. A use-after-free needs a specific allocation and free sequence to line up, which a single crafted request usually cannot arrange. Where a request path does trigger it reliably, that path is the finding; otherwise it belongs to a sanitizer build or a fuzzer, and claiming otherwise would be claiming a test that was not run.
CVSS 9.2 CRITICAL. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.
| Attack vector | networkreachable over the network, with no local access needed |
|---|---|
| Privileges required | noneneeds no credentials at all |
| User interaction | nonecan be triggered with nobody interacting with the page or request |
| Base vector | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| Weakness | CWE-416 |
This describes the vulnerability. It says nothing about whether your systems run it.
EPSS puts the probability of exploitation in the next 30 days at 1.0000, which places it in the top 1% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.
| EPSS probability | 1.0000 |
|---|---|
| Percentile | 1.000 — top 1% |
| Added to KEV | 2026-10-26 |
|---|---|
| Days exploited | 12 |
| Federal remediation due | not set |
| Ransomware use | no known ransomware campaign use |
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
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 lead to remote code execution (RCE).
Web application penetration testing · API security testing · every service