Skip to main content
VulnerabilityPublished

CVE-2026-69148: MLflow · CreateModelVersion source validation does not check READ permission on referenced run_id

Affects mlflowSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 3.15.0 soon.

Data as of 20 Nov 2026, 17:35 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.15.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade mlflow to 3.15.0.

Affected software

ProductAffectedFixed in
Bitnamimlflowpkg:bitnami/mlflowOther threatsAffected
  • <3.15.0
Fixed in
  • 3.15.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade MLflow to version 3.15.0 or later, where this issue is fixed. Since a patch is available and the vulnerability is resolved in the official release, applying the official fix is the recommended remediation.

Description

MLflow versions prior to 3.15.0 contain a vulnerability in the CreateModelVersion functionality where source validation does not properly check READ permissions on the referenced run_id. This allows authenticated users to create a model version that references another user's artifact directory and read files without the required permissions. The issue is fixed in version 3.15.0.

References

Community reviews

Loading reviews…