CISA KEV 19 Aug 2026: 1 exploited flaw in MLflow

Conceptual illustration: A sculptural neural-network lattice and machine-learning compute module inside a precision shield, patch plates on connected nodes. Headline: AI PLATFORM SECURITY.

AI-generated illustration by CyberShitty. Not a photograph or a document from the organisations named.

On 19 August 2026, CISA added 1 actively exploited vulnerability affecting MLflow to its Known Exploited Vulnerabilities catalog. If you run any of these products, patch or mitigate now — exploitation is already happening.

CVE-2026-64849Federal deadline 02 Sep 2026

MLflow Server-Side Request Forgery Vulnerability

MLflow / MLflow / CWE-918

MLflow contains a server-side request forgery vulnerability that can allow attackers to reach internal or cloud metadata services and receive response_status and response_body.

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.

github.com · github.com · nvd.nist.gov

In this section

MLflow Server-Side Request Forgery Vulnerability