CVE-2026-109618
CRITICALCISA KEVEPSS 100th pctlDescription
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).
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 100% of all known CVEs.
Remediation due: 2026-10-29
References
Related Vulnerabilities
Other CWE-416 (Use After Free) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-109619 | High | 8.1 | 100% | KEV | Fix |
| CVE-2019-0708 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-31166 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2015-5119 | Critical | 9.8 | 99% | KEV | - |
| CVE-2010-3962 | High | 8.1 | 97% | KEV | - |
| CVE-2021-34833 | High | 7.8 | 96% | - | - |
Common questions
How do I fix CVE-2026-109618?
Published advisories record a fix for 64 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-109618 being actively exploited?
Yes. CVE-2026-109618 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2026-10-29. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2026-109618?
CVE-2026-109618 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-109618 affect?
Published advisories record a fix for php8.2 (Debian), php8.4 (Debian), apcu-panel (Rocky), apcu-panel (Red Hat / RHEL), and 60 more. The list on this page is capped, so there may be more.
Embed a live status badge for CVE-2026-109618
Markdown
[](https://tridentstack.com/cve/CVE-2026-109618)HTML
<a href="https://tridentstack.com/cve/CVE-2026-109618"><img src="https://tridentstack.com/cve/badge/CVE-2026-109618.svg" alt="CVE-2026-109618"></a>This vulnerability is actively exploited in the wild
TridentStack Control detects known-exploited CVEs across your Linux fleet and prioritizes their patches. 200 endpoints free forever.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-05.