Skip to content
Fencer Intel
medium 5.8

CVE-2025-52967 json

MLFlow SSRF via gateway_proxy_handler

published last yr. modified 4mo ago also BIT-mlflow-2025-52967 , EUVD-2025-18888 , GHSA-wxj7-3fx5-pp9m , PYSEC-2025-52

cvss
5.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation.

Patch / fix

  • pypi mlflow 2.22.2, 3.1.0
  • bitnami mlflow 3.1.0
  • lfprojects MLflow 3.1.0

Is CVE-2025-52967 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
GitHub 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
OSV 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi mlflow
>=3.0.0rc0, <3.1.0
<2.22.2
<3.1.0
3.1.0
2.22.2
bitnami mlflow
<3.1.0
3.1.0

Affected products

  • lfprojects MLflow

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.