CVE-2026-64849: MLflow Server-Side Request Forgery Vulnerability
What it is
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.
What to do
Treat this as urgent. Identify every affected system, starting with anything internet-facing, and apply the vendor fix or mitigation within days. If you cannot patch quickly, isolate or disable the affected service and watch for signs of compromise.
- Priority
- Act now: Patch or mitigate internet-facing systems within days.
- Severity (CVSS)
- 9.3 critical
- CISA assessment (SSVC)
- actively exploited; attackers can automate it at scale; partial control or data exposure
- Exploit probability (EPSS, 30 days)
- 9.8%, higher than 95% of all CVEs
- Added to CISA KEV
- 19 August 2026
- CISA fix-by date
- 2 September 2026 (US federal agencies; a sensible deadline for everyone)
- Ransomware use
- Not known
- Weakness
- CWE-918
References
- NIST NVD entry
- CISA KEV entry
- github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939
- github.com/mlflow/mlflow/issues/24179
- github.com/mlflow/mlflow/pull/24258
- github.com/mlflow/mlflow/releases/tag/v3.15.0
- github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849
Sources: CISA Known Exploited Vulnerabilities · FIRST Exploit Prediction Scoring System (EPSS) · NIST National Vulnerability Database · CISA Vulnrichment (SSVC), via the CVE Program. This product uses data from the NVD API but is not endorsed or certified by the NVD. Summaries are machine-written from CISA’s description; treat the vendor’s advisory as the authority for fixes.