{"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-14279 in the wild and no public exploit code.","fix":"Upgrade mlflow to 3.5.0 or later.","what":"CVE-2025-14279 is a high-severity vulnerability in Lfprojects Mlflow, published on 12 Jan 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-2025-14279 and fix it if it is affected.\n\nWhat it is: CVE-2025-14279 is a high-severity vulnerability in Lfprojects Mlflow, published on 12 Jan 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: There is no known exploitation of CVE-2025-14279 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 3.5.0\n- mlflow (PyPI): affected all versions; fixed in 3.5.0\n- mlflow (PyPI): affected all versions; fixed in 3.5.0\n- mlflow (PyPI): affected all versions; fixed in 3.5.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-2025-14279/ (Markdown: https://insights.sbomify.com/CVE-2025-14279/index.md)","id":"CVE-2025-14279","markdown":"https://insights.sbomify.com/CVE-2025-14279/index.md","name":"CVE-2025-14279","record":{"aliases":["BIT-mlflow-2025-14279","GHSA-pgqp-8h46-6x4j","PYSEC-2026-1656"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MLflow REST server","requires_auth":"none","summary":"Attackers can bypass Same-Origin Policy via DNS rebinding to query, update, or delete MLflow experiments, leading to data exfiltration or manipulation.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"mlflow","vendor":"lfprojects"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"MLFlow versions up to and including 3.4.0 are vulnerable to DNS rebinding attacks due to a lack of Origin header validation in the MLFlow REST server. This vulnerability allows malicious websites to bypass Same-Origin Policy protections and execute unauthorized calls against REST endpoints. An attacker can query, update, and delete experiments via the affected endpoints, leading to potential data exfiltration, destruction, or manipulation. The issue is resolved in version 3.5.0.","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":"DNS Rebinding Vulnerability in mlflow/mlflow","id":"CVE-2025-14279","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"lfprojects:mlflow","products":["lfprojects:mlflow"],"type":"other","year":"2025"},"n_packages":4,"n_references":2,"next":{"headline":"PixelYourSite \u003c= 11.1.5 - Sensitive Information Exposure via Log File","id":"CVE-2025-14280"},"packages":[{"ecosystem":"Bitnami","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2025-14279"},{"ecosystem":"PyPI","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-pgqp-8h46-6x4j"},{"ecosystem":"PyPI","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-pgqp-8h46-6x4j"},{"ecosystem":"PyPI","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-1656"}],"prev":{"headline":"HT Slider for Elementor \u003c= 1.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2025-14278"},"products":["mlflow/mlflow"],"published":"2026-01-12","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-01-12","vendors":["mlflow"]},"summary":"Attackers can bypass Same-Origin Policy via DNS rebinding to query, update, or delete MLflow experiments, leading to data exfiltration or manipulation.","url":"https://insights.sbomify.com/CVE-2025-14279/"}