CVE-2026-64849Known exploitationPublic exploitNetwork attack vectorHinoki check available

Unauthenticated full-read SSRF via webhook redirects

Published Aug 17, 2026 · Updated Aug 20, 2026

Server-side request forgery in MLflow before 3.15.0 allows remote attackers to read internal HTTP responses via webhook tests. The POST /api/2.0/mlflow/webhooks/{id}/test path validates only the original webhook URL in _validate_webhook_url(), but mlflow/webhooks/delivery.py follows redirects and re-resolves the hostname without pinning or re-validating the connected peer IP. On default Tracking Server deployments, the endpoint is unauthenticated and reflects response_status and response_body, enabling reads from loopback, private-network, or cloud metadata services.

CVSS severity9.3
Critical
EPSS probability16.41%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Server-side request forgery in MLflow before 3.15.0 allows remote attackers to read internal HTTP responses via webhook tests. The POST /api/2.0/mlflow/webhooks/{id}/test path validates only the original webhook URL in _validate_webhook_url(), but mlflow/webhooks/delivery.py follows redirects and re-resolves the hostname without pinning or re-validating the connected peer IP. On default Tracking Server deployments, the endpoint is unauthenticated and reflects response_status and response_body, enabling reads from loopback, private-network, or cloud metadata services.

The record

CVE
CVE-2026-64849
Published
Aug 17, 2026
Updated
Aug 20, 2026
Vendor
MLflow Project
Product
MLflow
Classifications
CWE-918, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Exploitation reportedCISA Known Exploited Vulnerabilities Catalog entry
  3. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.15.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

MLflow Project · MLflowversion=< 3.15.0

Published CVSS scores

9.3GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo