Servers and applications
CVE-2026-69146
LogInputs endpoint bypasses per-run UPDATE authorization in MLflow basic-auth
- Severity
- Medium 4.3
- Published
- 4 Aug 2026
- Last changed
- 16 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.16.0
- Exploit chance
- 0.4% in the next 30 daysHigher than 33% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Missing authorization (CWE-862)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N- Also known as
- GHSA-3p64-6gvh-82v5
- Sources
- Project advisories (GitHub)
Description
Append to description:
When MLflow is deployed with the built-in basic-auth plugin (--app-name basic-auth), any authenticated user can inject arbitrary dataset records into another user's run by calling POST /api/2.0/mlflow/runs/log-inputs. The LogInputs proto handler is absent from the BEFORE_REQUEST_HANDLERS map in mlflow/server/auth/init.py, so the before-request hook skips authorization entirely and the request succeeds. Standard write endpoints on the same run -- such as POST /api/2.0/mlflow/runs/log-metric -- correctly return HTTP 403.
MLflow's basic-auth app gates every HTTP handler through a before-request hook (_before_request) that looks up the relevant permission validator in BEFORE_REQUEST_VALIDATORS. Validators are built from the BEFORE_REQUEST_HANDLERS dictionary, which maps each protobuf request class to a callable.
Affected software
| Software | Affected versions |
|---|---|
MLflowServers and applications · github:mlflow/mlflow |
|
About MLflow
Python library
- Monthly downloads
- 30M+MLflow
- Weekly downloads (PyPI)
- 5,332,947PyPI Stats, 15 Nov 2026
- GitHub stars
- 28,816GitHub, 15 Nov 2026
- Forks
- 6,611GitHub, 15 Nov 2026
- Latest release
- v3.18.0GitHub, 15 Nov 2026
- Released
- 4 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- First published on GitHub
- 5 Jun 2018GitHub
Vulnerabilities in MLflow
- In our list
- 89
- Published in the last 12 months
- 37
- Critical, last 12 months
- 7
- High, last 12 months
- 15
- Known exploited
- 1
- CVE-2026-127202MLflow < 3.18.0 Path Traversal via model_id in log_outputs APIMedium 6.3 12 Nov 2026
- CVE-2026-118628Server-Side Request Forgery in the MLflow tracking server via client-supplied artifact locations and model version sourcesHigh 8.2 3 Nov 2026
- CVE-2026-118627MLflow SHAP load_explainer Deserialization of Untrusted Data Remote Code Execution VulnerabilityHigh 7.8 3 Nov 2026
- CVE-2026-118626MLflow Tracking Server Issues Missing Authorization Privilege Escalation VulnerabilityMedium 5.4 3 Nov 2026
- CVE-2026-118625MLflow Tracking Server Missing Authorization Privilege Escalation VulnerabilityMedium 6.3 3 Nov 2026
- CVE-2026-118624MLflow Tracking Server Jobs Missing Authorization Information Disclosure VulnerabilityMedium 5.4 3 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-69146
- GitHub Advisory Database https://github.com/advisories/GHSA-3p64-6gvh-82v5
- github.com https://github.com/mlflow/mlflow/security/advisories/GHSA-3p64-6gvh-82v5