Findings

Vulnerability · CVE-2025-15381

In the latest version of mlflow/mlflow, when the app is enabled, tracing and assessment endpoints are not protected by permission validators.

Published Mar 27, 2026 · corrected/updated Oct 12, 2026 · lfprojects mlflow · evidence confidence high

In the latest version of mlflow/mlflow, when the app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with on the experiment, to read trace information and create assessments for traces they should not have access to. This vulnerability impacts confidentiality by exposing trace metadata and integrity by allowing unauthorized creation of assessments. Deployments using are affected.

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-15381 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 7.1, EPSS 0.3%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-200, CWE-425. 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 27, 2026 · NIST NVD

    Detected

    In the latest version of mlflow/mlflow, when the app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with on the experiment, to read trace information and create assessments for traces they should not have access to. This vulnerability impacts confidentiality by exposing trace metadata and integrity by all

  2. Oct 12, 2026 · NIST NVD

    Updated

    In the latest version of mlflow/mlflow, when the app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with on the experiment, to read trace information and create assessments for traces they should not have access to. This vulnerability impacts confidentiality by exposing trace metadata and integrity by all

Affected

  • cpe lfprojects/mlflowversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2025-15381

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-15381

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2025-15381

    In the latest version of mlflow/mlflow, when the app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with on the experiment, to read trace information and cr

    nvd.nist.gov

References