Exploited CVEs / CVE-2026-109618
CVE-2026-109618
PHP Memory Corruption Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies must remediate by 2026-10-29; 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 October 26, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
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-10-26
- 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.
What the press says about CVE-2026-109618
Trusted-source coverage, pulled live from their own feeds.
From the Senserva blog
- Patch and Vulnerability Intelligence
July 10, 2026 · Kyle, Senserva Dev Team
CISA required action
Federal remediation due date: 2026-10-29.
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. 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.