CVE-2026-8147: Authorization Bypass in mlflow/mlflow
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 beforerequest 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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mlflow/mlflowto a version that resolves this vulnerability.Fixed in 3.14.0 - Compensating control
If upgrading immediately is not possible, restrict access to the MLflow trace API endpoints (read/delete/modify traces) to only users/groups that should have experiment-level trace permissions, e.g., via network controls or an API gateway/ACL placed in front of those endpoints.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-8147?
The severity of CVE-2026-8147 is rated high with a score of 8.1.
How do I fix CVE-2026-8147?
To fix CVE-2026-8147, upgrade MLflow to version 3.14.0 or higher where the vulnerability is addressed.
What does CVE-2026-8147 affect?
CVE-2026-8147 affects MLflow versions prior to 3.14.0 when run with authentication enabled.
What type of vulnerability is CVE-2026-8147?
CVE-2026-8147 is an authorization bypass vulnerability that allows authenticated users to bypass experiment-level authorization controls.
What operations are impacted by CVE-2026-8147?
CVE-2026-8147 impacts trace operations, including reading, deleting, and modifying traces.