CVE-2026-116690

MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source

Direct impact is arbitrary local file read as the MLflow server process. Confirmed read targets include:

• /etc/passwd
• SQLite tracking databases readable by the process (e.g., mlflow-auth.db or basic_auth.db)
• Environment variables or configurations stored on disk
• /home/user/.bash_history

Threat model: An attacker who can reach the MLflow tracking server HTTP port can read arbitrary files readable by the MLflow server process. On unauthenticated MLflow deployments, this is directly exploitable without credentials. On auth-enabled deployments, any authenticated user (even low-privileged or "read-only" accounts, depending on default RBAC configurations allowing model creation) can use the primitive. Leaked credential stores may enable offline password attacks or broader administrative compromise.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-116690 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.17.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-116690? CVE-2026-116690 is a high-severity path traversal vulnerability in mlflow (pip), affecting versions >= 3.10.0, < 3.17.0. It is fixed in 3.17.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-116690? CVE-2026-116690 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of mlflow are affected by CVE-2026-116690? mlflow (pip) versions >= 3.10.0, < 3.17.0 is affected.
4. Is there a fix for CVE-2026-116690? Yes. CVE-2026-116690 is fixed in 3.17.0. Upgrade to this version or later.
5. Is CVE-2026-116690 exploitable, and should I be worried? Whether CVE-2026-116690 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-116690 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-116690? Upgrade mlflow to 3.17.0 or later.

Other vulnerabilities in mlflow