Critical MLflow and FUXA Vulnerabilities Exploited: Cloud Credentials at Risk
- Severity
- HIGH
- Affected component
- mlflow (npm)
- Affected versions
- < 3.15.0 or < 3.15.0
- Patched version
- Not yet available
Two critical vulnerabilities in MLflow and FUXA are being actively exploited to steal cloud credentials and secrets. MLflow is an open-source AI platform, and FUXA is a web-based SCADA/HMI software for industrial automation.
What happened
Attackers are exploiting two critical vulnerabilities in MLflow and FUXA to steal cloud credentials and secrets. The first vulnerability, tracked as CVE-2026-64849, is an unauthenticated Server-Side Request Forgery (SSRF) in MLflow that allows attackers to issue HTTP requests to arbitrary internal cloud metadata endpoints and extract sensitive data. This affects MLflow versions less than 3.15.0. The second vulnerability, CVE-2026-25895, is a missing authentication for a critical function and path traversal in FUXA, allowing unauthenticated remote attackers to write arbitrary files to the server file system and achieve remote code execution. The affected version range for FUXA has not been authoritatively published yet.
CISA has warned that threat actors are actively exploiting CVE-2026-64849 in MLflow, a critical DNS-rebinding server-side request forgery (SSRF) bypass in MLflow's outbound webhook delivery. This vulnerability can be used by attackers without privileges to remotely access internal services or cloud metadata configurations on unpatched instances.
What to do about it
- Upgrade to the latest versions of MLflow and FUXA as soon as they are available.
- Review cloud credentials and secrets for any signs of compromise.
- Monitor the primary sources for updates on the FUXA vulnerability, as no authoritative version range has been published yet.
- Ensure that MLflow instances are updated to version 3.15.0 or later to mitigate CVE-2026-64849.
How 0Day would have caught this
mlflow is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
You are affected if you are using MLflow versions less than 3.15.0. The affected version range for FUXA has not been authoritatively published yet.
What should I do right now?
Upgrade to the latest versions of MLflow and FUXA as soon as they are available, and review cloud credentials and secrets for any signs of compromise.
Has this been exploited in the wild?
Yes, both vulnerabilities are being actively exploited.