Cross-run lineage tampering via unguarded LogInputs
Published Aug 17, 2026 · Updated Aug 18, 2026
Missing authorization in MLflow Project MLflow before 3.15.0 lets remote authenticated users alter run lineage via POST /api/2.0/mlflow/runs/log-inputs. In basic-auth deployments, mlflow/server/auth/init.py omits the LogInputs protobuf handler from BEFORE_REQUEST_HANDLERS, so the before-request hook never calls validate_can_update_run for that route and accepts a target run_id from another user. Exploitation requires any valid basic-auth account and affects integrity of dataset_inputs provenance records for other users' runs, but the published record does not show direct code execution, read access, or service interruption.
Summary
What happened
Missing authorization in MLflow Project MLflow before 3.15.0 lets remote authenticated users alter run lineage via POST /api/2.0/mlflow/runs/log-inputs. In basic-auth deployments, mlflow/server/auth/init.py omits the LogInputs protobuf handler from BEFORE_REQUEST_HANDLERS, so the before-request hook never calls validate_can_update_run for that route and accepts a target run_id from another user. Exploitation requires any valid basic-auth account and affects integrity of dataset_inputs provenance records for other users' runs, but the published record does not show direct code execution, read access, or service interruption.
The record
- CVE
- CVE-2026-69146
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.15.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-3p64-6gvh-82v5 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo