Exploitation timeline
Threadlinqs has recorded 5 mlflow CVEs published between and . The busiest month was 2026-08 (3 new CVEs). 1 of them (20%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.
Most exploited vulnerabilities
Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 5 of 5 tracked mlflow CVEs.
- CVE-2026-64849critical 9.3KEVEPSS 9.8%
- CVE-2026-53995high 8.2EPSS 0.6%
- CVE-2026-2393high 7.1EPSS 0.3%
- CVE-2026-69146medium 6.5EPSS 0.2%
- CVE-2026-69148high 7.1EPSS 0.2%
Products affected
Threadlinqs normalises CPE and CNA product records across all 5 CVEs; 2 distinct mlflow products are affected. The most frequently affected:
- mlflow 4 CVEs
- mlflow/mlflow 1 CVE
Threat activity
1 tracked threat campaign reference mlflow products or exploit mlflow CVEs:
How to prioritise mlflow patching
This order follows the data Threadlinqs holds for mlflow, not a generic severity checklist:
- 1 of 5 mlflow CVEs (20%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2026-64849.
- Outside KEV, the highest EPSS scores are CVE-2026-53995 (0.6%), CVE-2026-2393 (0.3%), CVE-2026-69146 (0.2%).
- 1 CVE scores Critical and 3 High on CVSS v3 (maximum 9.3, average 7.6); sequence these after KEV and high-EPSS items.
- 2 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.
About this data
Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-28 and refresh daily.