Based on the description, it is inferred that MLflow versions before 3.14.0 have trace API endpoints that do not register the necessary authorization validators when authentication is enabled. Users can modify traces from experiments for which they have no permission, exposing sensitive information, damaging audit trails, and enabling unauthorized changes to experiment artifacts. The weakness is an authorization bypass (CWE‑284) caused by missing checks.

All installations of the open‑source MLflow platform that run any release prior to 3.14.0 with authentication activated are affected. The product is delivered through the mlflow/mlflow repository and is used in diverse environments without vendor differentiation beyond the core library.

The CVSS score of 8.1 categorizes the vulnerability as high severity, while an EPSS score of less than 1% indicates a very low but nonzero likelihood of exploitation. The issue is not listed in the CISA KEV catalog, suggesting no publicly documented exploit. Authenticated users can perform standard API calls to read, delete, or modify traces of experiments they do not have permission to access.