{"answers":{"affected":"4 open source packages ship an affected version, including mlflow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-11200 in the wild and no public exploit code.","fix":"Upgrade mlflow to a fixed version for your release line: 2.21.1 or 2.22.0rc0.","what":"CVE-2025-11200 is a high-severity authentication bypass vulnerability in Lfprojects Mlflow, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-11200 and fix it if it is affected.\n\nWhat it is: CVE-2025-11200 is a high-severity authentication bypass vulnerability in Lfprojects Mlflow, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-11200 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 2.21.1\n- mlflow (PyPI): affected all versions; fixed in 2.22.0rc0\n- mlflow (PyPI): affected all versions; fixed in 2.22.0rc0\n- mlflow (PyPI): affected all versions; fixed in 2.22.0rc0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-11200/ (Markdown: https://insights.sbomify.com/CVE-2025-11200/index.md)","id":"CVE-2025-11200","markdown":"https://insights.sbomify.com/CVE-2025-11200/index.md","name":"CVE-2025-11200","record":{"aliases":["BIT-mlflow-2025-11200","GHSA-6xj8-rrqx-r4cv","PYSEC-2026-1642"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow server","requires_auth":"none","summary":"Remote attackers can bypass authentication in MLflow due to weak password requirements, gaining unauthorized access to the system.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"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.\n\nThe 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.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MLflow Weak Password Requirements Authentication Bypass Vulnerability","id":"CVE-2025-11200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"auth_bypass","year":"2025"},"n_packages":4,"n_references":2,"next":{"headline":"MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2025-11201"},"packages":[{"ecosystem":"Bitnami","fixed":["2.21.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2025-11200"},{"ecosystem":"PyPI","fixed":["2.22.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-6xj8-rrqx-r4cv"},{"ecosystem":"PyPI","fixed":["2.22.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-6xj8-rrqx-r4cv"},{"ecosystem":"PyPI","fixed":["2.22.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-1642"}],"prev":{"headline":"Missing authorization in Security Director Policy Enforcer","id":"CVE-2025-11198"},"products":["MLflow"],"published":"2025-10-29","related":[{"cvss_score":9.3,"headline":"MLflow Server-Side Request Forgery","id":"CVE-2026-64849","kev_date_added":"2026-08-19","published":"2026-08-17"},{"cvss_score":10,"headline":"Command Injection in mlflow/mlflow","id":"CVE-2025-15379","kev_date_added":null,"published":"2026-03-30"},{"cvss_score":10,"headline":"Remote Code Execution due to Full Controlled File Write in mlflow/mlflow","id":"CVE-2024-0520","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":10,"headline":"Path Traversal: '\\..\\filename'","id":"CVE-2023-6977","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":10,"headline":"Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow","id":"CVE-2023-6709","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":10,"headline":"MLflow Arbitrary File Upload","id":"CVE-2023-6015","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":10,"headline":"MLflow Arbitrary File Write","id":"CVE-2023-6018","kev_date_added":null,"published":"2023-11-16"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["MLflow"]},"summary":"Remote attackers can bypass authentication in MLflow due to weak password requirements, gaining unauthorized access to the system.","url":"https://insights.sbomify.com/CVE-2025-11200/"}