{"answers":{"affected":"3 open source packages ship an affected version, including mlflow.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69146 exists.","fix":"Upgrade mlflow to 3.15.0 or later.","what":"CVE-2026-69146 is a medium-severity missing authorization vulnerability in mlflow, published on 17 Aug 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-69146 and fix it if it is affected.\n\nWhat it is: CVE-2026-69146 is a medium-severity missing authorization vulnerability in mlflow, published on 17 Aug 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-69146 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected all versions; fixed in 3.15.0\n- mlflow (npm): affected all versions; fixed in 3.15.0\n- mlflow (npm): affected all versions; fixed in 3.15.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-69146/ (Markdown: https://insights.sbomify.com/CVE-2026-69146/index.md)","id":"CVE-2026-69146","markdown":"https://insights.sbomify.com/CVE-2026-69146/index.md","name":"CVE-2026-69146","record":{"aliases":["BIT-mlflow-2026-69146","GHSA-3p64-6gvh-82v5","MINI-j6rc-4x44-q37w"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"MLflow AI platform","requires_auth":"low_privilege","summary":"Authenticated users can inject dataset inputs into other users' runs due to missing authorization checks in the LogInputs endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.13.0 until 3.15.0, LogInputs is absent from BEFORE_REQUEST_HANDLERS in the mlflow/server/auth package, allowing any authenticated user to call POST /api/2.0/mlflow/runs/log-inputs for another user's run_id and inject attacker-controlled DatasetInput records into the dataset_inputs lineage metadata without UPDATE permission. This issue is fixed in version 3.15.0.","ecosystems":["Bitnami","npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth","id":"CVE-2026-69146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"vLLM: Request-selected PyNvVideoCodec GPU decode bypasses static VRAM reservation","id":"CVE-2026-69147"},"packages":[{"ecosystem":"Bitnami","fixed":["3.15.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2026-69146"},{"ecosystem":"npm","fixed":["3.15.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-3p64-6gvh-82v5"},{"ecosystem":"npm","fixed":["3.15.0"],"introduced":["0"],"last_affected":[],"package":"mlflow","purl":"pkg:npm/mlflow","source":"GHSA-3p64-6gvh-82v5"}],"prev":{"headline":"KubePi: Insufficient per-cluster authorization checks in cluster management APIs","id":"CVE-2026-69129"},"products":["mlflow"],"published":"2026-08-17","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["mlflow"]},"summary":"Authenticated users can inject dataset inputs into other users' runs due to missing authorization checks in the LogInputs endpoint.","url":"https://insights.sbomify.com/CVE-2026-69146/"}