Browse / AI Framework and Platform Flaws / CVE-2026-2393
MLflow Has a Server-Side Request Forgery (SSRF) Vulnerability
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Server-side request forgery
- Affected
- mlflow (PyPI)
- CVSS
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- EPSS
- 0.3% chance of exploitation in 30 days
How it works, in short
MLflow's webhook creation accepts an arbitrary URL that the backend then posts to, letting an authenticated user reach internal services and metadata endpoints. (Our summary, written by a model. The source text is below.)
Details
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-2393
- https://github.com/mlflow/mlflow/commit/64aa0ab7207f9c649b59ba1a5f40d82196817389
- https://github.com/mlflow/mlflow
- https://huntr.com/bounties/04ef100d-06b5-4a70-95b1-b7be23aa8150
Source: GitHub Advisory Database, used under CC BY 4.0.