{"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-8147 exists.","fix":"Upgrade mlflow to a fixed version for your release line: 3.14.0 or 3.13.0rc0.","what":"CVE-2026-8147 is a high-severity missing authorization vulnerability in Lfprojects Mlflow, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8147 and fix it if it is affected.\n\nWhat it is: CVE-2026-8147 is a high-severity missing authorization vulnerability in Lfprojects Mlflow, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8147 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 3.14.0\n- mlflow (PyPI): affected from 2.14.0rc0; fixed in 3.13.0rc0\n- mlflow (PyPI): affected from 2.14.0rc0; fixed in 3.13.0rc0\n- mlflow (PyPI): affected from 2.14.0rc0; fixed in 3.13.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-8147/ (Markdown: https://insights.sbomify.com/CVE-2026-8147/index.md)","id":"CVE-2026-8147","markdown":"https://insights.sbomify.com/CVE-2026-8147/index.md","name":"CVE-2026-8147","record":{"aliases":["BIT-mlflow-2026-8147","CLSA-2026-1788442606","GHSA-2cm6-r77w-6g96","PYSEC-2026-3686"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"MLflow machine learning library","requires_auth":"low_privilege","summary":"Authenticated users can bypass authorization checks to read, modify, or delete traces in unauthorized MLflow experiments when authentication is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack proper authorization validators. This allows any authenticated user to bypass experiment-level authorization controls on all trace operations, including reading, deleting, and modifying traces on experiments they do not have permission to access. The issue arises from the `_before_request` handler, which does not register authorization validators for trace endpoints, resulting in requests proceeding without validation. This vulnerability can expose sensitive data, destroy audit logs, and allow unauthorized modifications.","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":"Authorization Bypass in mlflow/mlflow","id":"CVE-2026-8147","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":"Privilege escalation in NAVER MYBOX Explorer","id":"CVE-2026-8148"},"packages":[{"ecosystem":"Bitnami","fixed":["3.14.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2026-8147"},{"ecosystem":"PyPI","fixed":["3.13.0rc0"],"introduced":["2.14.0rc0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-2cm6-r77w-6g96"},{"ecosystem":"PyPI","fixed":["3.13.0rc0"],"introduced":["2.14.0rc0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-2cm6-r77w-6g96"},{"ecosystem":"PyPI","fixed":["3.13.0rc0"],"introduced":["2.14.0rc0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"PYSEC-2026-3686"}],"prev":{"headline":"WholesaleX \u003c= 3.0.8 - Unauthenticated Limited Privilege Escalation via 'process_registration'","id":"CVE-2026-8145"},"products":["mlflow/mlflow"],"published":"2026-07-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-07-02","vendors":["mlflow"]},"summary":"Authenticated users can bypass authorization checks to read, modify, or delete traces in unauthorized MLflow experiments when authentication is enabled.","url":"https://insights.sbomify.com/CVE-2026-8147/"}