ZeroDay Findings
Sign inSign up

Findings

CVE-2025-14287

A command injection vulnerability exists in mlflow/mlflow versions before v3.7.0, specifically in the file at lines 161-167.

Published Mar 16, 2026 · corrected/updated Jul 15, 2026 · lfprojects mlflow · evidence confidence high

A command injection vulnerability exists in mlflow/mlflow versions before v3.7.0, specifically in the file at lines 161-167. The vulnerability arises from the direct interpolation of user-supplied container image names into shell commands without proper sanitization, which are then executed using . This allows attackers to execute arbitrary commands by supplying malicious input through the parameter of the CLI. The issue affects environments where MLflow is used, including development setups, CI/CD pipelines, and cloud deployments.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2025-14287 is a high public vulnerability record for lfprojects mlflow. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether lfprojects mlflow is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: lfprojects/mlflow. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 8.8, EPSS 1.5%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-78, CWE-94. Sources contributing to this record: cve_org, epss, nvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 16, 2026 · NIST NVD

    Detected

    A command injection vulnerability exists in mlflow/mlflow versions before v3.7.0, specifically in the file at lines 161-167. The vulnerability arises from the direct interpolation of user-supplied container image names into shell commands without proper sanitization, which are then executed using . This allows attackers to execute arbitrary commands by supplying malicious input through the paramet

  2. Jul 15, 2026 · NIST NVD

    Updated

    A command injection vulnerability exists in mlflow/mlflow versions before v3.7.0, specifically in the file at lines 161-167. The vulnerability arises from the direct interpolation of user-supplied container image names into shell commands without proper sanitization, which are then executed using . This allows attackers to execute arbitrary commands by supplying malicious input through the paramet

Affected

  • cpe lfprojects/mlflowversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2025-14287

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-14287

    30-day exploitation probability 1.5%

    first.org
  • NIST NVDVulnerability recordCVE-2025-14287

    A command injection vulnerability exists in mlflow/mlflow versions before v3.7.0, specifically in the file at lines 161-167. The vulnerability arises from the direct interpolation of user-supplied container image names into shell commands without pr

    nvd.nist.gov

References