Skip to content
Distributed Risk
Desk

MLflow Server-Side Request Forgery Vulnerability Added to CISA KEV

CISA KEV · 3 sources

What's on the official record

CISA's Known Exploited Vulnerabilities catalog records CVE-2026-64849, an MLflow server-side request forgery vulnerability. The catalog states the vulnerability can allow attackers to reach internal or cloud metadata services and receive response_status and response_body. CISA lists CWE-918 and a dateAdded of 19 August 2026, with a dueDate of 2 September 2026 for federal civilian agencies. The catalogVersion is 2026.10.23.

The CVE record names a fixed version: mlflow < 3.15.0. The catalog does not record known ransomware use for this vulnerability. FIRST's EPSS model estimates a score of 0.100 (p96, 2026-10-23). CISA's ADP records SSVC exploitation=active, automatable=yes, impact=partial.

Assessment

For a platform or AI-stack owner, the record lets you check whether any MLflow deployment in your stack runs a version below 3.15.0, the fixed version the CVE record names. The catalog's dueDate of 2 September 2026 is the federal remediation deadline, and the SSVC exploitation=active line from CISA's ADP is a reason to treat the upgrade as time-sensitive rather than routine. You can decide to patch to 3.15.0 or later, or isolate any MLflow instance that reaches internal or cloud metadata services until it is upgraded.

For a deal team, the record gives you a concrete diligence question for any target that runs MLflow: which version is deployed, and whether it predates 3.15.0. The catalog's statement that the vulnerability can reach internal or cloud metadata services is a reason to scope whether a target's MLflow instance is network-reachable from untrusted input. You can price or condition a transaction on confirmation of the fixed version before close.

What would change this call

A vendor or target confirming an MLflow version at or above 3.15.0 would resolve the exposure question the record raises. A CISA update to the catalog entry — a revised dueDate, a changed catalogVersion, or a ransomware designation — would change what a reader checks next.

What to check next

CheckWhy
MLflow version in deployed stacksThe CVE record names mlflow < 3.15.0 as affected
Network reachability of MLflow to metadata servicesThe catalog states the vulnerability can reach internal or cloud metadata services
CISA KEV catalog for updates to this entrydueDate and catalogVersion may change

Confidence

Filed 23 October 2026 from the record dated 19 August 2026.

Sources

[1] MLflow Server-Side Request Forgery Vulnerability — https://nvd.nist.gov/vuln/detail/CVE-2026-64849

[2] CVE record CVE-2026-64849 — https://www.cve.org/CVERecord?id=CVE-2026-64849

[3] CISA Known Exploited Vulnerabilities Catalog — https://www.cisa.gov/known-exploited-vulnerabilities-catalog

InquireAgents read this note with get_note cyb-20260819-cve-2026-64849. Connect an agent