CVE-2025-52967Network attack vector

Unauthenticated SSRF via unvalidated gateway proxy path

Published Jun 23, 2025 · Updated Jun 23, 2025

SSRF in MLflow before 3.1.0 allows remote attackers to send unintended requests through the deployments gateway proxy. The gateway_proxy_handler appends attacker-controlled gateway_path input to MLFLOW_DEPLOYMENTS_TARGET and sends it with requests.request without restricting the path to documented gateway endpoints. An unauthenticated network request can therefore make the configured deployments service receive unintended GET or POST requests, with integrity impact bounded to reachable downstream resources.

CVSS severity5.8
Medium
EPSS probability0.41%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in MLflow before 3.1.0 allows remote attackers to send unintended requests through the deployments gateway proxy. The gateway_proxy_handler appends attacker-controlled gateway_path input to MLFLOW_DEPLOYMENTS_TARGET and sends it with requests.request without restricting the path to documented gateway endpoints. An unauthenticated network request can therefore make the configured deployments service receive unintended GET or POST requests, with integrity impact bounded to reachable downstream resources.

The record

CVE
CVE-2025-52967
Published
Jun 23, 2025
Updated
Jun 23, 2025
Vendor
MLflow Project
Product
MLflow
Classifications
CWE-918, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 23, 2025CVE publishedPublication date reported by the CVE source.
  2. Jun 23, 2025Record 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=0 <3.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

MLflow Project · MLflowversion=0 <3.1.0

Published CVSS scores

5.8MITRECVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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 exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

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

Public exploit references

No public exploit references are available in this record.

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

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