Live › vulnerability › CVE-2026-64849
Go to dashboardMLflow Tracking Server's unauthenticated POST /api/2.0/mlflow/webhooks/{id}/test endpoint is an SSRF. The URL guard is bypassed through HTTP redirects and DNS rebinding, so an attacker can reach cloud metadata (169.254.169.254) or internal services and read the response body. The usual result is theft of cloud IAM credentials. CVSS 9.3 (CNA GitHub). Exploited in the wild and listed in CISA KEV.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
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.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| MLflow MLflow | vendor | – | – |
| mlflow | pip | >= 3.10.0, < 3.15.0 | 3.15.0 |
| lfprojects mlflow | vendor | >= 3.3.0, < 3.15.0 | 3.15.0 |
pip show mlflow (or mlflow --version) on each host or container image running mlflow server3.10.0 and < 3.15.0 are vulnerable3.15.0 or later (pip install -U mlflow>=3.15.0)169.254.169.254, enforce IMDSv2, and put the server behind authentication or a VPNEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Posts are quoted with a link to the original. They are data to us, never instructions.
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.
CISA 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-64849")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.