MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding
CVE-2026-64849 · GHSA-7gwp-5pfp-969j · published 2026-08-17 · updated 2026-10-02
- Severity
- Critical
- CVSS score
- 9.3
- Chance of exploitation (EPSS)
- 10.0%
- Fixed in
- 3.15.0
Known exploited
CISA added this to its Known Exploited Vulnerabilities catalog on 2026-08-19; US federal agencies had until 2026-09-02 to act. CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk.
- Exploitation Exploited in the wild
- Automatable Yes
- Technical impact Partial
- CISA SSVC
An unauthenticated attacker who can reach the tracking server makes the server issue HTTP requests to arbitrary internal/loopback/cloud-metadata endpoints and reads the responses via /test: cloud instance-metadata (e.g. AWS IMDS IAM credentials), internal-only admin services behind the network boundary, and internal port/host scanning. The event-driven delivery path gives the same SSRF blindly; /test makes it full-read. This is an incomplete fix of the PR #20747 guard, confirmed present on the latest release (3.13.0) and on master. Not a duplicate of CVE-2025-14279 (browser-side rebinding CSRF, CWE-352).
Upgrade mlflow to 3.15.0 or later.
Fixed in https://github.com/mlflow/mlflow/pull/24258 (commit ba94952247), which adds connection-time SSRF protection (SSRFProtectedHTTPAdapter): the peer IP of each connected socket is validated against public-IP rules immediately after connect(), before any TLS/HTTP exchange. This covers the redirect targets as well (each redirect opens a new connection through the protected pool), closing both the 302-read and 307/308-write variants and the DNS-rebinding TOCTOU.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mlflow | PyPI | >= 3.3.0, < 3.15.0 | 3.15.0 |
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- Criticallobe-chat `/api/proxy` endpoint Server-Side Request Forgery vulnerability@lobehub/chat
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalMLflow allows unauthorized access to multipart upload endpoints when the `--serve-artifacts` mode is enabledmlflow
- CriticalMLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command Executionmlflow
- Criticalmlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorizationmlflow
- CriticalMlflow: Command Injection when serving models with enable_mlserver=Truemlflow
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.