CVE-2025-14287: Command Injection Vulnerability in mlflow Package

mlflow Updated 17 Apr 2026

Summary

16/04/2026
Yes i
High
Not published

CVE-2025-14287: Command Injection in mlflow/mlflow. Affects mlflow versions < 3.7.0. Fixed in 3.7.0. How to fix ↓

Also tracked for

The same CVE-2025-14287 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

MLflow is an open-source platform designed for managing the machine learning lifecycle, including experimentation, reproducibility, and deployment. It provides tools for tracking experiments, packaging code into reproducible runs, and sharing and deploying models. However, certain versions of MLflow are vulnerable to command injection, which can compromise the security of environments utilizing this package.

Vulnerability Detail

A command injection vulnerability exists in mlflow/mlflow versions prior to v3.7.0, specifically in the mlflow/sagemaker/init.py file at lines 161-167. This vulnerability arises from the direct interpolation of user-supplied container image names into shell commands without proper sanitization. As a result, attackers can execute arbitrary commands by providing malicious input through the --container parameter of the CLI. This issue poses significant risks in environments where MLflow is deployed, including development setups, CI/CD pipelines, and cloud deployments.

How To Fix

Minimum fixed version

3.7.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid using the --container parameter with untrusted or user-supplied input until the package is updated to a secure version. Always validate and sanitize any input that may be used in shell commands.

Conclusion

The command injection vulnerability CVE-2025-14287 in the mlflow package poses significant security risks. It is crucial for users to update to version 3.7.0 or later to mitigate these risks. Until an update can be applied, users should implement workarounds to safeguard their environments.

See every vulnerability recorded for mlflow →

Share this vulnerability

FAQ

CVE-2025-14287 is a command injection vulnerability found in the mlflow package that allows attackers to execute arbitrary commands.

All versions of mlflow prior to v3.7.0 are affected by this vulnerability.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By uploading your manifest file like package-lock.json, you can check for vulnerabilities without needing to access the code.

If an immediate update is not possible, avoid using the --container parameter with untrusted input and ensure that all user inputs are validated and sanitized.

More information can be found in the official GitHub repository and vulnerability databases, which provide details on the issue and its implications.

Related vulnerabilities

Recent vulnerabilities recorded for mlflow.

How To Fix

Minimum fixed version

3.7.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback