KEV Lag Tracker → CVE-2026-109618. Data verified against the official CISA KEV catalog and the National Vulnerability Database.

CISA added CVE-2026-109618 (PHP Group PHP) to the Known Exploited Vulnerabilities catalog on October 26, 2026. It was publicly known for 5 days before CISA confirmed active exploitation. A KEV listing is CISA’s official confirmation that a vulnerability is being exploited in the wild.

The Record

CVECVE-2026-109618
Vendor / productPHP Group PHP
VulnerabilityPHP Memory Corruption Vulnerability
CVSS base score9.8
EPSS probability the day before the KEV listing99.98% (100.0% percentile)
NVD publication dateOctober 21, 2026
Added to CISA KEVOctober 26, 2026
Lag (public → KEV listing)5 days
Federal patch deadlineOctober 29, 2026
Known ransomware useNo

Measured against the 1769 entries in our tracker with verified publication dates, CVE-2026-109618 was flagged faster than 77% of them.

What CISA Reported

CISA describes the flaw as follows: “PHP contains an out-of-memory corruption vulnerability that allows for unauthenticated remote code execution.”

Federal Patch Deadline

Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-109618 by October 29, 2026 — a 3-day remediation window from the KEV listing date. Private organizations are not bound by that deadline; CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

What EPSS Forecast Before the Confirmation

The EPSS forecast (FIRST’s daily estimate of the probability a CVE will be exploited within 30 days) put CVE-2026-109618 at 99.98% on the day before CISA confirmed active exploitation — the 100.0% percentile of all scored CVEs that day. That places it inside the top 10% of EPSS risk before the confirmation: this one the forecast saw coming.

EPSS for CVE-2026-109618Value
Probability the day before the KEV listing99.98%
Percentile the day before the KEV listing100.0%
Probability today (November 9, 2026)100.00%
Percentile today100.0%

Today’s figure is not evidence that the forecast worked: EPSS reacts to the KEV listing itself, so the score for any confirmed-exploited CVE tends to rise after CISA acts. Only the eve-of-listing number was available to a defender making the call. Across every KEV entry we track, we measured how often that number was high — see the EPSS accuracy analysis.

How This Compares

We do not yet track enough PHP Group entries to publish a vendor median (the threshold is five with verified publication dates), so the reference here is the catalog as a whole:

Across all tracked KEV entriesValue
Entries with verified publication dates1769
Median lag (disclosure → KEV listing)232 days
Exploited within 7 days of disclosure25%
Tied to known ransomware campaigns19%

Other Recent PHP Group KEV Additions

CVEProductAdded to KEVLag (days)Ransomware
CVE-2026-109619PHPOctober 26, 20265No
CVE-2024-4577PHPJune 12, 20243⚠️ Yes

Frequently Asked Questions

What is CVE-2026-109618?

CVE-2026-109618 is a vulnerability in PHP Group PHP (PHP Memory Corruption Vulnerability) that CISA added to its Known Exploited Vulnerabilities catalog on October 26, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild.

How long was CVE-2026-109618 public before CISA confirmed exploitation?

5 calendar days, measured from its NVD publication date to the date CISA added it to the KEV catalog.

What is the federal patch deadline for CVE-2026-109618?

U.S. federal agencies must remediate CVE-2026-109618 by October 29, 2026, a 3-day window from the KEV listing date. Private organizations are not bound by that deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

Is CVE-2026-109618 used in ransomware campaigns?

CISA has not flagged CVE-2026-109618 as known to be used in ransomware campaigns. That field reflects confirmed campaign use, not the absence of risk.

What was the EPSS score for CVE-2026-109618 before it was confirmed as exploited?

99.98% — the probability EPSS assigned on the day before CISA added CVE-2026-109618 to the KEV catalog, placing it in the 100.0% percentile of all scored CVEs that day. That is inside the top 10% of EPSS risk. Its score today is higher in most cases because EPSS reacts to the KEV listing itself, so only the eve-of-listing figure reflects what a defender could have acted on.

Is a 5-day lag typical?

The median across all 1769 KEV entries we track with verified publication dates is 232 days, so CVE-2026-109618 is below the catalog median.

Related Coverage

Primary Sources

How We Track This

This page is generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No date or figure on this page is estimated or taken from a third-party source — they come directly from CISA and NVD records. Free to cite with attribution to CVEDaily (CC BY 4.0).