CVE-2026-64849
MLflow webhook-test SSRF via redirect re-validation bypass
- Severity
- critical
- Affected product
- MLflow
- Affected versions
- MLflow ≤ 3.13.0
- Fixed in
- MLflow 3.14.0
- Added to NewScan
- 2026-08-18
- Detected by
- NewScan — free, self-hosted
How NewScan reports it
COMPONENT VERSION RANGE
NewScan fingerprints MLflow from its response and reports this CVE when the detected version falls inside the affected range below.
Added 2026-08-23 once a version source existed (the MLflow tech_signatures row, /version as a gated version_from). Range resolved from the GHSA bound (<=3.13.0) and deliberately NOT from NVD's <3.15.0 text - the two disagree and D153's instruction is the GHSA wins; corroborated by measurement, on v3.14.0 the vulnerable route answers 405 (2026-08-18). The bug: POST /api/2.0/mlflow/webhooks/{id}/test validates the initial webhook URL and never re-pins the resolved IP, so a 302/307/308 to an internal target is followed. Version-match only - the row numbers the deployment; EXPLOITING the redirect-follow is the ssrf_tools engine item (backlog D143), and the anonymous-tracking-API precondition ships separately as the interfaces /api/2.0/mlflow/experiments/search row, which deliberately claims no CVE.
References
Scan for this yourself — local, in-band scanning is free.
Get NewScan (FREE) →