MLFLOW · CVE-2023-6974 · AI agents & MCP
FIX → 2.9.2
MLflow versions before 2.9.2 let a user make the server send HTTP requests to destinations the user chooses. An attacker can reach internal HTTP services and, in the worst case on a cloud instance, reach a path to remote code execution.
first public Dec 20, 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 that accepts requests from users who should not be able to direct its outbound HTTP calls. The risk is highest where the server runs on a cloud instance that exposes internal metadata or services. Teams on 2.9.2 or later, or who only use MLflow locally with no untrusted users, can skip it.
Not affected if fixed-version, local-only-use
Who cares cloud, mlflow, python, self-hosted
pip show mlflow and treat anything below 2.9.2 as affected.Upgrade to 2.9.2
A malicious user could use this issue to access internal HTTP(s) servers and in the worst case (ie: aws instance) it could be abused to get a remote code execution on the victim machine.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.
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.
mlflow to 2.9.2 or later.