Skip to content
Fencer Vulns
medium 5.9

CVE-2025-0453 json

Denial of Service through Batched Queries in GraphQL in mlflow/mlflow

published 2025-03-20 19 mo ago modified 2026-09-08 2 mo ago also BIT-mlflow-2025-0453 , EUVD-2025-6836 , GHSA-49m6-vrr9-2cqm , PYSEC-2026-1637

cvss
5.9
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
11.3%
EPSS 11.3% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

In mlflow/mlflow version 2.17.2, the `/graphql` endpoint is vulnerable to a denial of service attack. An attacker can create large batches of queries that repeatedly request all runs from a given experiment. This can tie up all the workers allocated by MLFlow, rendering the application unable to respond to other requests. This vulnerability is due to uncontrolled resource consumption.

Patch / fix

  • bitnami mlflow 2.18.0

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

11.31% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.com https://huntr.com/bounties/788327ec-714a-4d5c-83aa-8df04dd7612b referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi mlflow
<=2.17.2
no fix listed
bitnami mlflow
>=2.17.2, <2.18.0
2.18.0

Affected products

  • mlflow mlflow/mlflow

Classification

Weakness
  • CWE-410 Insufficient Resource Pool
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns 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.