Skip to main content
VulnerabilityPublished

CVE-2026-69146: MLflow · LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth

Affects mlflowSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 3.15.0 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

Severity
Medium

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

EPSS
0.3% chance of exploitation in 30 days – higher than 33% 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 authorization bypass vulnerability has been fixed. No other mitigations are indicated by the vendor advisory.

Description

MLflow versions from 3.13.0 up to but not including 3.15.0 contain a vulnerability where the LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth mode. This allows any authenticated user to call the POST /api/2.0/mlflow/runs/log-inputs endpoint for another user's run and inject attacker-controlled DatasetInput records into the dataset_inputs lineage metadata without having UPDATE permission. The issue is fixed in version 3.15.0.

References

Community reviews

Loading reviews…