9.3

CVE-2026-64849: MLflow Server-Side Request Forgery Vulnerability

CVSS: 9.3v3.1CriticalKEVAnalyzed
AliasesGHSA-7gwp-5pfp-969jBIT-mlflow-2026-64849PYSEC-2026-3687
Published 17-08-2026Last modified 02-10-2026

Vulnerability summary

CVE-2026-64849 is a critical (CVSS 9.3) Server-Side Request Forgery (SSRF) vulnerability in MLflow. It is known to be exploited: CISA lists it, first on 19-08-2026. EPSS estimates a 9.84% chance of exploitation in the next 30 days, higher than 95.5% of scored vulnerabilities. 1 public exploit is recorded.

Overall risk
85/100
0100
Critical · default modelHow is this calculated?
CVSS score
9.3/10
010
Critical · v3.1 (CVE.org)
EPSS score
9.84%
0%100%
Low · -6.57 pp in 30 days
KEVListedCISA
RansomwareNone recordedNo known use recorded
Public exploits1github

Timeline

  1. 17-08-2026
    PublishedVulnerability first disclosed.
  2. 19-08-2026
    Added to CISA KEVMLflow Server-Side Request Forgery Vulnerability
  3. 02-09-2026
    CISA remediation dueApply mitigations per vendor instructions.
  4. 02-10-2026
    Last modifiedVulnerability information updated.

Description

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

9.84%

Chance of exploitation in the next 30 days

Percentile

96%

Versus all other CVEs

30-day change

-6.57 pp

From 16.41% on 21-09-2026

21-09-202621-10-2026
EPSS score
9.84%

Known exploited

Compare KEV catalogs
CISA KEVListed
Added
19-08-2026
Federal due date
02-09-2026

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. github.com/mlflow/mlflow/pull/24258 github.com/mlflow/mlflow/issues/24179 nvd.nist.gov/vuln/detail/CVE-2026-64849

Public exploits

1 found
  • githubUnverified

    Mlflow

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

Chainguard1 product
  • mlflow< 3.16.0-r0
Lfprojects1 product
Mlflow1 product
PyPI1 product
  • mlflow≥ 3.3.0, < 3.15.0 | < 3.15.0
Wolfi1 product
  • mlflow< 3.16.0-r0

5 vendors · 5 products

References

11 links
Show all 11 references