MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth (CVE-2026-69146)
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.
AI Analysis
Technical Summary
MLflow, an open source AI engineering platform, has an authorization bypass vulnerability in versions prior to 3.15.0. Specifically, the LogInputs endpoint is not included in BEFORE_REQUEST_HANDLERS in the mlflow/server/auth package from versions 3.13.0 to 3.15.0, allowing authenticated users to bypass per-run UPDATE authorization. This enables attackers to inject DatasetInput records into another user's run metadata without proper permissions. The vulnerability is resolved in MLflow version 3.15.0.
Potential Impact
An authenticated user can inject arbitrary DatasetInput records into the dataset_inputs lineage metadata of another user's run without having UPDATE permission. This could lead to unauthorized modification of lineage metadata, potentially affecting data integrity and audit trails within MLflow projects.
Mitigation Recommendations
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.
MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth (CVE-2026-69146)
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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
MLflow, an open source AI engineering platform, has an authorization bypass vulnerability in versions prior to 3.15.0. Specifically, the LogInputs endpoint is not included in BEFORE_REQUEST_HANDLERS in the mlflow/server/auth package from versions 3.13.0 to 3.15.0, allowing authenticated users to bypass per-run UPDATE authorization. This enables attackers to inject DatasetInput records into another user's run metadata without proper permissions. The vulnerability is resolved in MLflow version 3.15.0.
Potential Impact
An authenticated user can inject arbitrary DatasetInput records into the dataset_inputs lineage metadata of another user's run without having UPDATE permission. This could lead to unauthorized modification of lineage metadata, potentially affecting data integrity and audit trails within MLflow projects.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-mlflow-2026-69146
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-69146"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
- Cvss Version
- null
Threat ID: 6a885f27acd9273b493f8197
Added to database: 08/21/2026, 14:22:31 UTC
Last enriched: 08/21/2026, 14:37:21 UTC
Last updated: 08/21/2026, 22:52:14 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.