CVE-2026-64849KEV · OVERDUECWE-918ssrf

MLflow Server-Side Request Forgery Vulnerability

Critical · published August 18, 2026

Patch now

Confirmed exploited, and the score agrees

CVSS calls it critical at 9.3. It is confirmed in active exploitation. It sits in the 95.6th percentile for exploit probability.

52
days past CISA
deadline
CVSS v3.1
9.3
EPSS
10%
Percentile
95.6
In the wild
Confirmed
What it is

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Starting in 3.3.0 and 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.

The record
Technical detail
CVSS v3.1
9.3 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
CVSS v4.0
Not supplied
EPSS
0.10017 · 95.6th percentile
Weakness
CWE-918 · Server-Side Request Forgery (SSRF)
Published
2026-08-18T02:17Z
KEV added
2026-08-19 · due 2026-09-02
Affected products (1)
ProductVersionsFixed in
lfprojects/mlflow≥ 3.3.0, < 3.15.03.15.0
References (6)
EPSS history
Timeline
  • 17 AUG 21:16Z
    MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)
    cvelistv5