mlflow · MLflow · published 2026-08-17

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

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-69146 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 33% of all CVEs. This MLflow vulnerability: CVSS 6.5 (v3.1). Fixed upstream in MLflow 3.16.0, 3.15.0. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in MLflow 3.16.0, 3.15.0.

Patch events

  1. This monthSecurity release

    AI toolingMLflow

    MLflow security releases: 3.16.0, 3.15.0

    Upgrade to 3.16.03.15.0

    Why: CVE-2026-69148: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (34th pct)FIRST EPSS v2026.06.15
CVSS base score6.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.13.0 until 3.15.0, LogInputs is absent from BEFORE_REQUEST_HANDLERS in the mlflow/server/auth package, allowing any authenticated user to call POST /api/2.0/mlflow/runs/log-inputs for another user's run_id and inject attacker-controlled DatasetInput records into the dataset_inputs lineage metadata without UPDATE permission. This issue is fixed in version 3.15.0.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →