CVE-2026-2393

published 11 May 2026 · updated 11 Nov 2026

Server-Side Request Forgery (SSRF) in mlflow/mlflow

8.1HighCVSS 7.1EPSS 0%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in MLflow 3.10.0 and 3.9.0.

A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The `_create_webhook()` function in `mlflow/server/handlers.py` accepts a user-controlled `url` parameter without validation, and the `_send_webhook_request()` function in `mlflow/webhooks/delivery.py` sends HTTP POST requests to this attacker-controlled URL. This allows an authenticated attacker to force the MLflow backend to send HTTP requests to internal services, cloud metadata endpoints, or arbitrary external servers. The lack of input sanitization, URL scheme filtering, or allowlist validation on the webhook URL enables exploitation, potentially leading to cloud credential theft, internal network access, and data exfiltration.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MLflowMLflow<3.10.03.10.0
lfprojectsmlflow<3.9.03.9.0

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in MLflow, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-2393 severity on Zeptric[![CVE-2026-2393](https://zeptric.io/badge/cve/CVE-2026-2393.svg)](https://zeptric.io/cve/CVE-2026-2393)