Improper Access Control Affecting mlflow package, versions <3.16.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-MLFLOW-19829202
- published16 Sept 2026
- disclosed2 Jul 2026
Introduced: 2 Jul 2026
CVE-2026-8147 (opens in a new tab)How to fix?
Upgrade Chainguard mlflow to version 3.16.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream mlflow package and not the mlflow package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.