MLFLOW · CVE-2023-6014 · AI agents & MCP
FIX → 2.8.0
MLflow versions before 2.8.0 let an attacker create user accounts without passing the authentication check. The sources do not say what the new account can then reach, beyond what a normal MLflow account can access.
first public Nov 16, 2023 · 1 public exploit · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running an MLflow tracking server with its authentication feature enabled are exposed, since the bypass targets the authentication requirement. Installations that use MLflow locally without the auth layer are not described as affected by the sources. The sources do not say how the bypass is triggered.
Not affected if auth-not-enabled, mlflow-below-2.8.0-absent
Who cares mlflow, python, self-hosted
pip show mlflow; anything below 2.8.0 is affected.mlflow.server.auth setup).Upgrade to 2.8.0
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirement.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
mlflow2.8.0GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.