CVE-2026-8147: CWE-284 Improper Access Control in mlflow 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 `_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.
AI Analysis
Technical Summary
CVE-2026-8147 describes an improper access control vulnerability (CWE-284) in MLflow's trace API endpoints in versions before 3.14.0. When authentication is enabled, the `_before_request` handler fails to register authorization validators for trace endpoints, enabling any authenticated user to bypass experiment-level authorization controls. This allows unauthorized users to perform read, delete, and modify operations on traces of experiments they should not access. The vulnerability impacts confidentiality and integrity of trace data and audit logs.
Potential Impact
The vulnerability allows any authenticated user to bypass authorization checks on trace operations, potentially exposing sensitive trace data, enabling unauthorized deletion or modification of traces, and compromising audit logs. This undermines the confidentiality and integrity of experiment trace data within MLflow environments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authentication to trusted users only and monitor usage of trace API endpoints to detect suspicious activity. Avoid enabling trace API access for users without explicit permissions. Follow vendor updates for patches addressing this issue.
CVE-2026-8147: CWE-284 Improper Access Control in mlflow mlflow/mlflow
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.
CVSS v3.0
Score 8.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-8147 describes an improper access control vulnerability (CWE-284) in MLflow's trace API endpoints in versions before 3.14.0. When authentication is enabled, the `_before_request` handler fails to register authorization validators for trace endpoints, enabling any authenticated user to bypass experiment-level authorization controls. This allows unauthorized users to perform read, delete, and modify operations on traces of experiments they should not access. The vulnerability impacts confidentiality and integrity of trace data and audit logs.
Potential Impact
The vulnerability allows any authenticated user to bypass authorization checks on trace operations, potentially exposing sensitive trace data, enabling unauthorized deletion or modification of traces, and compromising audit logs. This undermines the confidentiality and integrity of experiment trace data within MLflow environments.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authentication to trusted users only and monitor usage of trace API endpoints to detect suspicious activity. Avoid enabling trace API access for users without explicit permissions. Follow vendor updates for patches addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- @huntr_ai
- Date Reserved
- 2026-05-08T02:45:28.857Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a46231427e9c797198a9fcd
Added to database: 07/02/2026, 08:36:36 UTC
Last enriched: 07/02/2026, 08:51:22 UTC
Last updated: 07/03/2026, 02:23:20 UTC
Views: 13
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.