MLflow <3.17.0 - Unauthenticated SSRF via Third-Party (TruLens) Scorer
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. References: https://github.com/mlflow/mlflow/security/advisories/GHSA-2wqp-q3c6-ccj5 https://github.com/mlflow/mlflow/commit/bac30b4148c4f40045b4d4db07ae60ab3838803f https://github.com/mlflow/mlflow/pull/25890 https://github.com/mlflow/mlflow/releases/tag/v3.17.0 https://nvd.nist.gov/vuln/detail/CVE-2026-115886 Remediation: Upgrade MLflow to 3.17.0 or later, which constrains third-party scorer classes and their constructor kwargs.
Used 20 times · 10 assets checked · domain, subdomain, ipv4