{"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-2024-6838 exists.","fix":"Upgrade mlflow to 2.14.0 or later.","what":"CVE-2024-6838 is a medium-severity denial of service vulnerability in Lfprojects Mlflow, published on 20 Mar 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-2024-6838 and fix it if it is affected.\n\nWhat it is: CVE-2024-6838 is a medium-severity denial of service vulnerability in Lfprojects Mlflow, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6838 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected from 2.13.2; fixed in 2.14.0\n- mlflow (PyPI): affected all versions up to 2.13.2; no fix listed\n- mlflow (PyPI): affected all versions up to 2.13.2; no fix listed\n- mlflow (PyPI): affected all versions up to 2.13.2; no fix listed\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-2024-6838/ (Markdown: https://insights.sbomify.com/CVE-2024-6838/index.md)","id":"CVE-2024-6838","markdown":"https://insights.sbomify.com/CVE-2024-6838/index.md","name":"CVE-2024-6838","record":{"aliases":["BIT-mlflow-2024-6838","GHSA-q3gw-8236-5jw4","PYSEC-2026-1658"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow library","requires_auth":"none","summary":"Attackers can cause MLflow UI unresponsiveness by creating experiments with excessively long names or artifact locations, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"In mlflow/mlflow version v2.13.2, a vulnerability exists that allows the creation or renaming of an experiment with a large number of integers in its name due to the lack of a limit on the experiment name. This can cause the MLflow UI panel to become unresponsive, leading to a potential denial of service. Additionally, there is no character limit in the `artifact_location` parameter while creating the experiment.","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":"Uncontrolled Resource Consumption in mlflow/mlflow","id":"CVE-2024-6838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"denial_of_service","year":"2024"},"n_packages":4,"n_references":1,"next":{"headline":"Improper Regex Path Matching in corydolphin/flask-cors","id":"CVE-2024-6839"},"packages":[{"ecosystem":"Bitnami","fixed":["2.14.0"],"introduced":["2.13.2"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2024-6838"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.13.2"],"package":"mlflow","purl":null,"source":"GHSA-q3gw-8236-5jw4"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.13.2"],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-q3gw-8236-5jw4"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.13.2"],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-1658"}],"prev":{"headline":"Missing authorization in FunnelKit – Funnel Builder for WooCommerce Checkout","id":"CVE-2024-6836"},"products":["mlflow/mlflow"],"published":"2025-03-20","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["mlflow"]},"summary":"Attackers can cause MLflow UI unresponsiveness by creating experiments with excessively long names or artifact locations, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2024-6838/"}