{"answers":{"affected":"4 open source packages ship an affected version, including mlflow. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2651 exists.","fix":"Upgrade mlflow to a fixed version for your release line: 3.11.1, 3.10.0 or 3.11.0rc0.","what":"CVE-2026-2651 is a critical missing authorization vulnerability in Lfprojects Mlflow, published on 25 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-2651 and fix it if it is affected.\n\nWhat it is: CVE-2026-2651 is a critical missing authorization vulnerability in Lfprojects Mlflow, published on 25 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2651 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 3.11.1\n- mlflow (PyPI): affected all versions; fixed in 3.10.0\n- mlflow (PyPI): affected all versions; fixed in 3.10.0\n- mlflow (PyPI): affected all versions; fixed in 3.11.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-2026-2651/ (Markdown: https://insights.sbomify.com/CVE-2026-2651/index.md)","id":"CVE-2026-2651","markdown":"https://insights.sbomify.com/CVE-2026-2651/index.md","name":"CVE-2026-2651","record":{"aliases":["BIT-mlflow-2026-2651","CLSA-2026-1787146516","CLSA-2026-1788334607","GHSA-8c7q-86fq-vvmh","PYSEC-2026-2220"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"MLflow machine learning library","requires_auth":"low_privilege","summary":"Attackers can overwrite other users' artifacts in MLflow when artifact serving is enabled, potentially leading to model poisoning and code execution.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-1220","name":"Insufficient Granularity of Access Control"},{"id":"CWE-862","name":"Missing Authorization"}],"description":"A vulnerability in MLflow versions \u003c=3.10.1.dev0 allows unauthorized access to multipart upload (MPU) endpoints when the `--serve-artifacts` mode is enabled. The authorization logic does not enforce resource-level permission checks for `/mlflow-artifacts/mpu/*` endpoints, enabling attackers to overwrite artifacts belonging to other users. This can lead to unauthorized cross-user writes, model supply chain poisoning, and arbitrary code execution when compromised models are loaded. The issue is resolved in version 3.10.0.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Missing Authorization Validation in mlflow/mlflow","id":"CVE-2026-2651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"missing_authorization","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Authentication Bypass in mlflow/mlflow","id":"CVE-2026-2652"},"packages":[{"ecosystem":"Bitnami","fixed":["3.11.1"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2026-2651"},{"ecosystem":"PyPI","fixed":["3.10.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-8c7q-86fq-vvmh"},{"ecosystem":"PyPI","fixed":["3.10.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-8c7q-86fq-vvmh"},{"ecosystem":"PyPI","fixed":["3.11.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-2220"}],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2026-2650"},"products":["mlflow/mlflow"],"published":"2026-05-25","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["mlflow"]},"summary":"Attackers can overwrite other users' artifacts in MLflow when artifact serving is enabled, potentially leading to model poisoning and code execution.","url":"https://insights.sbomify.com/CVE-2026-2651/"}