MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Prior to 3.15.0, the unauthenticated POST /api/2.0/mlflow/webhooks/{id}/test endpoint calls _validate_webhook_url() in mlflow/utils/validation.py only for the original URL while mlflow/webhooks/delivery.py follows redirects and re-resolves the hostname without pinning the validated address, allowing attackers to reach internal or cloud metadata services and receive response_status and response_body. This issue is fixed in version 3.15.0.
References
| Link | Resource |
|---|---|
| https://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939 | Patch |
| https://github.com/mlflow/mlflow/issues/24179 | Exploit Issue Tracking Mitigation |
| https://github.com/mlflow/mlflow/pull/24258 | Issue Tracking Patch |
| https://github.com/mlflow/mlflow/releases/tag/v3.15.0 | Release Notes |
| https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j | Exploit Vendor Advisory |
| https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849 | US Government Resource |
Configurations
History
No history.
Information
Published : 2026-08-17 22:17
Updated : 2026-08-20 19:16
NVD link : CVE-2026-64849
Mitre link : CVE-2026-64849
CVE.ORG link : CVE-2026-64849
JSON object : View
Products Affected
lfprojects
- mlflow
CWE
CWE-918
Server-Side Request Forgery (SSRF)
