SB2026080340 - Server-Side Request Forgery (SSRF) in MLflow



SB2026080340 - Server-Side Request Forgery (SSRF) in MLflow

Published: August 3, 2026

Security Bulletin ID SB2026080340
CSH Severity
High
Patch available
YES
Number of vulnerabilities 1
Exploitation vector Remote access
Highest impact Data manipulation

Breakdown by Severity

High 100%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 1 vulnerability.


1) Server-Side Request Forgery (SSRF) (CVE-ID: CVE-2026-64849)

CWE-ID: CWE-918 - Server-Side Request Forgery (SSRF)

CVSSv4: 8.8 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:N/SA:N]


The vulnerability allows a remote attacker to disclose sensitive information from internal services and perform limited server-side requests to internal endpoints.

The vulnerability exists due to server-side request forgery (SSRF) in the MLflow webhook delivery and test_webhook endpoint when following HTTP redirects or re-resolving hostnames after validating the original webhook URL. A remote attacker can create a webhook pointing to an attacker-controlled HTTPS endpoint and trigger the unauthenticated test request to disclose sensitive information from internal services and perform limited server-side requests to internal endpoints.

On default servers, the webhook API is exposed without authentication, the first hop must use HTTPS, and the synchronous /api/2.0/mlflow/webhooks/{id}/test endpoint reflects the upstream response body to the caller. DNS rebinding can also bypass the validation because the validated IP is not pinned to the connection.


Remediation

Install update from vendor's website.