MLflow Server-Side Request Forgery
What to do
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.
CISA deadline 2026-09-02 · passed 8 days ago · applies to US federal civilian agencies; used elsewhere as a reference SLA
What happened
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.
Who is affected
MLflow MLflow. Affected version ranges are listed in the vendor advisory and the NVD entry linked under Sources.
Weakness class: CWE-918.
Timeline
- Added to CISA KEVExploitation in the wild confirmed by CISA
- CISA remediation deadlinepassed 8 days ago
Sources
- NVD entry for CVE-2026-64849 nvd.nist.gov/vuln/detail/CVE-2026-64849
- CISA Known Exploited Vulnerabilities catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
- github.com github.com/mlflow/mlflow/pull/24258
- github.com github.com/mlflow/mlflow/issues/24179
- cisa.gov www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- cisa.gov www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- nvd.nist.gov nvd.nist.gov/vuln/detail/CVE-2026-64849