Is CVE-2025-14287 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-14287 being exploited in the wild.

How severe is CVE-2025-14287?

High severity, with a CVSS score of 8.8, published 16 March 2026.

Which products and versions are affected?

mlflow (PyPI) ECOSYSTEM:introduced=0,fixed=3.8.0rc0.

Is there a fix for CVE-2025-14287?

Yes. mlflow (PyPI): upgrade to 3.8.0rc0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-14287 attacked?

It is attacked over the network or with local access, in a software library.

Am I affected by CVE-2025-14287?

Check whether you run mlflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-14287: MLflow command injection in SageMaker container parameter

CVE-2025-14287 · Severity: high · CVSS 8.8 · Published 2026-03-16

MLflow, a platform used to manage machine learning lifecycles, contains a security flaw that allows for unauthorized command execution. By providing a specially crafted container image name, an attacker can run arbitrary code on the underlying system. This could lead to a total compromise of the environment, including the theft of sensitive training data or disruption of machine learning pipelines.

Technologies: mlflow (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-14287 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-14287 being exploited in the wild.
How severe is CVE-2025-14287?: High severity, with a CVSS score of 8.8, published 16 March 2026.
Which products and versions are affected?: mlflow (PyPI) ECOSYSTEM:introduced=0,fixed=3.8.0rc0.
Is there a fix for CVE-2025-14287?: Yes. mlflow (PyPI): upgrade to 3.8.0rc0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-14287 attacked?: It is attacked over the network or with local access, in a software library.
Am I affected by CVE-2025-14287?: Check whether you run mlflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

mlflow (PyPI): upgrade to 3.8.0rc0 or later
```
pip install "mlflow>=3.8.0rc0"
```

Technical details

A command injection vulnerability exists in MLflow's SageMaker integration module (`mlflow/sagemaker/__init__.py`). The root cause is the direct interpolation of user-supplied container image names into shell commands executed via `os.system()` without proper sanitization. An attacker can exploit this by providing a malicious string to the `--container` CLI parameter. This allows for arbitrary code execution in the context of the MLflow process. The vulnerability is addressed in MLflow version 3.7.0.

Affected products

MLflow MLflow before 3.7.0
Red Hat OpenShift AI (RHOAI) Affected

Identifiers

CVE-2025-14287
GHSA-xch3-2f9x-wh9f
PYSEC-2026-2661

Timeline

2025-01-01: other: Initial Red Hat VEX release date
2026-03-15: disclosed: Reported via huntr.dev and Red Hat Bugzilla
2026-03-16: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.