{"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-115886 exists.","fix":"Upgrade mlflow to 3.17.0 or later.","what":"CVE-2026-115886 is a medium-severity vulnerability in mlflow, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-115886 and fix it if it is affected.\n\nWhat it is: CVE-2026-115886 is a medium-severity vulnerability in mlflow, published on 23 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115886 exists.\n\nAffected packages and fixed versions:\n- mlflow (Bitnami): affected from 3.12.0; fixed in 3.17.0\n- mlflow (PyPI): affected from 3.12.0rc0; fixed in 3.17.0\n- mlflow (PyPI): affected from 3.12.0rc0; fixed in 3.17.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-115886/ (Markdown: https://insights.sbomify.com/CVE-2026-115886/index.md)","id":"CVE-2026-115886","markdown":"https://insights.sbomify.com/CVE-2026-115886/index.md","name":"CVE-2026-115886","record":{"aliases":["BIT-mlflow-2026-115886","GHSA-2wqp-q3c6-ccj5"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-470","name":"Use of Externally-Controlled Input to Select Classes or Code"}],"description":"MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0rc0 until 3.17.0, the scorer invoke, register, and GenAI evaluate endpoints, including unauthenticated POST /ajax-api/3.0/mlflow/scorer/invoke, accept serialized third-party scorer data that Scorer.model_validate_json resolves using a module-path allowlist without constraining the selected class or its constructor arguments. When optional trulens and trulens-providers-litellm packages are installed, an attacker can select mlflow.genai.scorers.trulens, choose a model URI outside MLflow's native provider registry so execution uses the LiteLLM fallback, and supply api_base and api_key values that cause the server to send an outbound request to an attacker-chosen or internal host with attacker-controlled headers and body. The vulnerable deserialization occurs before a tracking-store lookup or job submission. This issue is fixed in version 3.17.0.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-115886.yaml","stars":null,"title":"MLflow \u003c3.17.0 - Unauthenticated SSRF via Third-Party (TruLens) Scorer"}],"tier":"weaponised"},"has_fix":true,"headline":"MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints","id":"CVE-2026-115886","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"graphql-scalars PhoneNumber scalar is vulnerable to regular expression denial of service","id":"CVE-2026-115887"},"packages":[{"ecosystem":"Bitnami","fixed":["3.17.0"],"introduced":["3.12.0"],"last_affected":[],"package":"mlflow","purl":"pkg:bitnami/mlflow","source":"BIT-mlflow-2026-115886"},{"ecosystem":"PyPI","fixed":["3.17.0"],"introduced":["3.12.0rc0"],"last_affected":[],"package":"mlflow","purl":null,"source":"GHSA-2wqp-q3c6-ccj5"},{"ecosystem":"PyPI","fixed":["3.17.0"],"introduced":["3.12.0rc0"],"last_affected":[],"package":"mlflow","purl":"pkg:pypi/mlflow","source":"GHSA-2wqp-q3c6-ccj5"}],"prev":{"headline":"LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output","id":"CVE-2026-115885"},"products":["mlflow"],"published":"2026-10-23","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["mlflow"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-115886/"}