Servers and applications
CVE-2026-8147
In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack proper authorization validators. This allows any authenticated user to bypass experiment-level authorization controls on all trace operations, including reading, deleting, and modifying traces on experiments they do not have permission to access. The issue arises from the `_before_request`…
- Severity
- High 8.1
- Published
- 2 Jul 2026
- Last changed
- 25 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.14.0
- Exploit chance
- 0.5% in the next 30 daysHigher than 46% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N- Sources
- NVD
Description
In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack proper authorization validators. This allows any authenticated user to bypass experiment-level authorization controls on all trace operations, including reading, deleting, and modifying traces on experiments they do not have permission to access. The issue arises from the _before_request handler, which does not register authorization validators for trace endpoints, resulting in requests proceeding without validation. This vulnerability can expose sensitive data, destroy audit logs, and allow unauthorized modifications.
Affected software
| Software | Affected versions |
|---|---|
MLflowServers and applications · cpe:a:lfprojects: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