# CISA KEV: MLflow / MLflow / MLflow Server-Side Request Forgery Vulnerability — retained record

> Retained cisa-kev record from cisa-kev.

Canonical: https://highsignal.app/data/records/43131acd10180a8a

[← sources](https://highsignal.app/data)


source: [cisa-kev](https://highsignal.app/data/cisa-kev) published 2026-08-19 00:00 ingested 2026-08-21 06:29

[original source ↗](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-64849)

## retained text



```
CVE: CVE-2026-64849
Vendor/project: MLflow
Product: MLflow
Known ransomware campaign use: Unknown
Due date: 2026-09-02
CWE: 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.
References: https://github.com/mlflow/mlflow/pull/24258 https://github.com/mlflow/mlflow/issues/24179 https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk https://nvd.nist.gov/vuln/detail/CVE-2026-64849
```



document fetched 2026-08-25 22:38 · canonical https://cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-64849
