{"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-2611 exists.","fix":"Upgrade mlflow to 3.10.0 or later.","what":"CVE-2026-2611 is a critical vulnerability in Lfprojects Mlflow, published on 19 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-2611 and fix it if it is affected.\n\nWhat it is: CVE-2026-2611 is a critical vulnerability in Lfprojects Mlflow, published on 19 May 2026. An attacker can exploit it over the internet without logging in, 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-2611 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected from 3.9.0; fixed in 3.10.0\n- mlflow (PyPI): affected from 3.9.0; fixed in 3.10.0\n- mlflow (PyPI): affected from 3.9.0; fixed in 3.10.0\n- mlflow (PyPI): affected from 3.9.0; fixed in 3.10.0\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-2611/ (Markdown: https://insights.sbomify.com/CVE-2026-2611/index.md)","id":"CVE-2026-2611","markdown":"https://insights.sbomify.com/CVE-2026-2611/index.md","name":"CVE-2026-2611","record":{"aliases":["BIT-mlflow-2026-2611","GHSA-67c5-x5mf-rppq","PYSEC-2026-418"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow machine learning library","requires_auth":"none","summary":"Remote attackers can bypass origin validation to modify MLflow Assistant configuration and execute arbitrary commands via a malicious webpage.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-940","name":"Improper Verification of Source of a Communication Channel"},{"id":"CWE-346","name":"Origin Validation Error"}],"description":"In MLflow version 3.9.0, the MLflow Assistant feature introduced improper origin validation in its /ajax-api endpoints. This vulnerability allows a remote attacker to exploit cross-origin requests from a malicious webpage to interact with the MLflow Assistant running on a victim's local machine. By bypassing the loopback-only restriction, the attacker can modify the Assistant's configuration to enable full access, which in turn allows the execution of arbitrary commands via the Claude Code sub-agent. This 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":"Improper Origin Validation in mlflow/mlflow","id":"CVE-2026-2611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"csrf","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Arbitrary File Read via Prompt Tag Source Validation Bypass in mlflow/mlflow","id":"CVE-2026-2614"},"packages":[{"ecosystem":"Bitnami","fixed":["3.10.0"],"introduced":["3.9.0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2026-2611"},{"ecosystem":"PyPI","fixed":["3.10.0"],"introduced":["3.9.0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-67c5-x5mf-rppq"},{"ecosystem":"PyPI","fixed":["3.10.0"],"introduced":["3.9.0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-67c5-x5mf-rppq"},{"ecosystem":"PyPI","fixed":["3.10.0"],"introduced":["3.9.0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-418"}],"prev":{"headline":"Gutenberg Blocks by Kadence Blocks \u003c= 3.5.32 - Missing Authorization","id":"CVE-2026-2608"},"products":["mlflow/mlflow"],"published":"2026-05-19","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":"Remote attackers can bypass origin validation to modify MLflow Assistant configuration and execute arbitrary commands via a malicious webpage.","url":"https://insights.sbomify.com/CVE-2026-2611/"}