Exploited CVEs / CVE-2026-109618
CVE-2026-109618
PHP Memory Corruption Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-10-29 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Internet-facing PHP is everywhere, exploit code was public before the fix, and the vendor shipped an emergency release: update every PHP host now, exposed ones first.
Actively exploited PHP Group PHP vulnerability, Critical severity, CVSS v3 9.8 (CVSS v4: 9.2). Added to the CISA KEV catalog 2026-10-26.
Updated November 16, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2026-109618
CVE-2026-109618 is one of two PHP flaws the researchers call PHP2Shell. The other is CVE-2026-109619. PHP shipped fixes on 21 October 2026 in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The bug is in out-of-memory handling. PHP uses longjmp() to abandon a request when an allocation fails. If that happens while request memory is only partly set up, cleanup code later trusts the half-built data. An attacker who can trigger an out-of-memory condition can turn that into unauthenticated remote code execution. PHP rates the risk highest for mod_php, because exploitation can happen before any application code runs. Your own code and plugins are therefore no protection, and a WAF or app-level fix does not address the root cause. The NCSC says all versions may be affected, so an old version number does not make a host safe. It also says not to limit discovery to outdated installs. watchTowr reports exploitation in the wild, and CISA lists it in KEV (added 2026-10-26). The Severity is Critical. NVD scores it CVSS 9.8, while the vendor-side and analyst write-ups cite 9.2 under CVSS 4.0, so the two numbers are the same flaw scored under different versions. Palo Alto's Unit 42 counted more than 22.6 million potentially exposed instances. That is why internet-facing hosts come first. I found no report of ransomware use. I also did not find the php.net advisory or the CISA KEV page in my search results, so confirm the fixed versions against PHP's own release notes.
Do this: Inventory every PHP runtime, including containers, CMS hosts and appliances that bundle PHP. Patch internet-facing mod_php hosts first to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or to your distro's backported package. Check the distro advisory, because backports keep older version strings. Restart Apache or php-fpm after patching so running workers load the fixed build. If you cannot patch yet, restrict exposure of those hosts and review web and PHP logs from before 21 October for out-of-memory errors, worker crashes and unexpected child processes. KEV exploitation means you should assume scanning has already reached you.
- NCSC-NL php2shell: operational information on CVE-2026-109618 and CVE-2026-109619: A government-run, recently updated tracker that restates PHP's advisory and lists fixed versions and distro package status.
- Unit 42 Threat Brief: Critical Vulnerabilities in PHP (Updated October 29): A respected analyst brief that explains the longjmp() mechanism and gives the exposure count of about 22.6 million instances.
- watchTowr: CVE-2026-109618 Exploited Remote Code Execution in PHP: A researcher FAQ that confirms exploitation in the wild and sets out the release timeline and the out-of-memory trigger.
AI-generated from public data, 2026-11-11. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-109618
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-109618
- Published
- 2026-10-21
- Last revised
- 2026-11-16
- Changes tracked
- 2
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA added CVE-2026-109618 to the KEV catalog on 2026-10-26, confirming exploitation in the wild, and that is the strongest signal. One day later, on 2026-10-27, EPSS jumped from 0.0% to 100.0%, so predicted exploit likelihood followed the confirmed evidence. Both signals now point the same direction, so treat this as an urgent patching priority today.
Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.
- 2026-10-21 EPSS first scored at 0.0%
- 2026-10-26 added to the CISA KEV catalog by CISA
- 2026-10-27 EPSS 0.0% to 100.0%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
From the Senserva blog
- An Ivanti VPN deadline lands today, Exchange's OWA problem hits day 20, and PHP2Shell reaches the firewalls
November 2, 2026 · Clay, Clay in the Morning - A PHP deadline, a Remote Desktop fix, and an Exchange problem still open
October 29, 2026 · Clay, Clay in the Morning - Patch and Vulnerability Intelligence
July 10, 2026 · Kyle, Senserva Dev Team
CISA required action
Federal remediation due date: 2026-10-29 (past due).
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.
Official fix for CVE-2026-109618
Update Php to version 8.2.35 or later. Update Php to version 8.3.36 or later. Update Php to version 8.4.27 or later. (Fixed-version data from NVD.)
Common questions about CVE-2026-109618
Is CVE-2026-109618 actively exploited?
Yes. CVE-2026-109618 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-26, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%.
What is the CISA deadline and required action for CVE-2026-109618?
CISA set the federal remediation due date at 2026-10-29, which has passed; treat any unremediated system as overdue. The verbatim required action: 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.
What fixes CVE-2026-109618?
Check the vendor's security advisory for the patched PHP versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-109618?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-109618's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).
Scope and sources
- More exploited PHP Group CVEs
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.