# CVE-2025-11200: mlflow Auth Bypass β€” Fixed in 2.22.0rc0 🐍 🐍 PyPI Not in CISA KEV HIGH severity # CVE-2025-11200 β€” mlflow HIGH [Fix: mlflow/mlflow@1f74f3f](https://github.com/mlflow/mlflow/commit/1f74f3f24d8273927b8db392c23e108576936c54) CVE-2025-11200 is a high-severity (CVSS 8.1) CWE-521 vulnerability in mlflow. A fix is available for mlflow β€” see the affected versions and patch details below. MLflow Weak Password Requirements Authentication Bypass Vulnerability Also known asBIT-mlflow-2025-11200[GHSA-6xj8-rrqx-r4cv](/vulnerability/GHSA-6xj8-rrqx-r4cv)PYSEC-2026-1642 Published Oct 29, 2025 Updated Oct 28, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 6, 2026 Β· OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-11200. ## EPSS Exploitation Probability [via FIRST.org β†—](https://www.first.org/epss/) 1.4%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs73th percentile β€” riskier than 73% of all scored CVEsHighest risk 0.00%0.66%1.33%1.99%0.2%1.4%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 1 pkg affected 🐍`mlflow` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages β€” download data is not available via public APIs for these ecosystems. ## Description MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of passwords. The issue results from weak password requirements. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26916. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 🐍PyPI `mlflow` all versions 2.22.0rc0`pip install --upgrade 'mlflow==2.22.0rc0'` ## Affected Products 1 product Β· 1 configurations Application `mlflow`lfprojects ≀ 2.21.0 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow, including transitive dependencies β€” a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update mlflow to 2.22.0rc0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range β€” O3 confirms CVE-2025-11200 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions MLflow Weak Password Requirements Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of passwords. The issue results from weak password requirements. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26916. O3 Security Β· Impact-Aware SCA ### Is CVE-2025-11200 in your dependencies? Find it across PyPI, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)