UTC
High

Server-Side Request Forgery in the MLflow tracking server via client-supplied artifact locations and model version sources

CVE-2026-118628 · GHSA-mr9f-g8qf-4w4j · published 2026-11-13

Severity
High
CVSS score
8.2
Chance of exploitation (EPSS)
Not scored
Fixed in
3.18.0
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

Internal reachability and port probing. The server opens a TCP connection to any host and port the client names. File read from internal file services. Against an internal FTP, SFTP or HDFS service that accepts the login supplied in the URI (or anonymous access), the client can list and download files through the artifact endpoints. File write to the same services. /ajax-api/2.0/mlflow/upload-artifact stores client-supplied content (up to 10 MB) through the same repository. Reading internal HTTP responses under --no-serve-artifacts. …

What to do

Upgrade mlflow to 3.18.0 or later.

Upgrade to MLflow 3.18.0 or later. 3.17.0 closes the paths described above (https://github.com/mlflow/mlflow/pull/25891). The tracking server refuses to connect to host-addressed artifact locations (ftp, sftp, hdfs, viewfs, http, https, host-bearing mlflow-artifacts, r2, b2, abfss) that name a host other than its configured --default-artifact-root or --artifacts-destination. The check applies when a client submits a location or source, when a stored location is used to serve artifacts, and inside server-side jobs. 3.18.0 closes a bypass of that check through the wasbs:// scheme (https://github.com/mlflow/mlflow/pull/27396). …

If you cannot upgrade yet

No configuration option disables the behavior in affected versions. Until upgrading: Do not expose the tracking server to untrusted networks, and enable authentication so that only trusted users can create experiments and model versions. Restrict the server's outbound network access to its artifact storage, and block internal ranges and the cloud metadata endpoint.

Affected
PackageRegistryAffectedFixed in
mlflowPyPI< 3.18.03.18.0

The impact, patch and workaround text comes from the advisory, shortened (published by MLflow). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].