MLflow Vulnerability Exploited for Cloud Credential Theft
MLflow SSRF vulnerability exploited in-the-wild to steal cloud credentials
A critical SSRF vulnerability (CVE-2026-64849, CVSS 9.3) in MLflow's unauthenticated model-registry webhooks API is being actively exploited to extract cloud credentials and secrets from cloud-hosted instances. All versions before 3.15.0 are affected, with CISA adding it to its KEV catalog and urging federal agencies to patch within two weeks.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Linux Foundation / MLflow Project?
Get an email when a new story names Linux Foundation / MLflow Project, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA critical Server-Side Request Forgery (SSRF) vulnerability in MLflow's unauthenticated webhooks API allowed attackers to pivot through the ML platform to extract cloud credentials and secrets without any authentication required. The root failure is twofold: a sensitive API endpoint was left exposed without authentication controls, and organizations failed to apply patches before active exploitation began. This matters because MLflow instances are commonly deployed in cloud environments with broad IAM permissions, meaning credential theft can rapidly escalate to full cloud account compromise. CISA's addition of this CVE to the Known Exploited Vulnerabilities catalog signals that this is not a theoretical risk — real-world attacks are already underway.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Cloud security posture management (CSPM and CNAPP)
Misconfigured cloud storage and over-permissive roles get caught before they leak.
Indicators of Compromise
Extracted by AI from the linked source. Not reviewed by an editor. How this works
- cve — CVE-2026-64849