{"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-2025-10279 exists.","fix":"Upgrade mlflow to a fixed version for your release line: 3.4.0 or 3.4.0rc0.","what":"CVE-2025-10279 is a high-severity vulnerability in Lfprojects Mlflow, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10279 and fix it if it is affected.\n\nWhat it is: CVE-2025-10279 is a high-severity vulnerability in Lfprojects Mlflow, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10279 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 3.4.0\n- mlflow (PyPI): affected all versions; fixed in 3.4.0rc0\n- mlflow (PyPI): affected all versions; fixed in 3.4.0rc0\n- mlflow (PyPI): affected all versions; fixed in 3.4.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-10279/ (Markdown: https://insights.sbomify.com/CVE-2025-10279/index.md)","id":"CVE-2025-10279","markdown":"https://insights.sbomify.com/CVE-2025-10279/index.md","name":"CVE-2025-10279","record":{"aliases":["BIT-mlflow-2025-10279","GHSA-4x5p-f36r-mxxr","PYSEC-2026-1639"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MLflow library","requires_auth":"low_privilege","summary":"An attacker with local write access to /tmp can exploit a race condition in MLflow's virtual environment creation to achieve arbitrary code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-379","name":"Creation of Temporary File in Directory with Insecure Permissions"}],"description":"In mlflow version 2.20.3, the temporary directory used for creating Python virtual environments is assigned insecure world-writable permissions (0o777). This vulnerability allows an attacker with write access to the `/tmp` directory to exploit a race condition and overwrite `.py` files in the virtual environment, leading to arbitrary code execution. The issue is resolved in version 3.4.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":"Privilege Escalation in mlflow/mlflow","id":"CVE-2025-10279","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"race_condition","year":"2025"},"n_packages":4,"n_references":2,"next":{"headline":"Incorrect Content Type Cross-Site Scripting Vulnerability","id":"CVE-2025-10280"},"packages":[{"ecosystem":"Bitnami","fixed":["3.4.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2025-10279"},{"ecosystem":"PyPI","fixed":["3.4.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-4x5p-f36r-mxxr"},{"ecosystem":"PyPI","fixed":["3.4.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-4x5p-f36r-mxxr"},{"ecosystem":"PyPI","fixed":["3.4.0rc0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-1639"}],"prev":{"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10278"},"products":["mlflow/mlflow"],"published":"2026-02-02","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-02-02","vendors":["mlflow"]},"summary":"An attacker with local write access to /tmp can exploit a race condition in MLflow's virtual environment creation to achieve arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2025-10279/"}