mlflow/mlflow: Insufficient Resource Pool
CVE-2025-0453 is a high-severity insufficient resource pool vulnerability in mlflow/mlflow from Mlflow, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected mlflow/mlflow versions: latest and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 11.3% chance of exploitation within 30 days, which is in the top 3.95% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Check which version of mlflow/mlflow you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Mlflow | mlflow/mlflow | latest and earlier | Not stated |
| Lfprojects | Mlflow | 2.17.2 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 3.0 | 5.9 | Medium | CNA (huntr.dev) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Resource Pool
The product's resource pool is not large enough to handle peak demand.
How developers prevent this class of flaw
- Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.
- Consider implementing a velocity check mechanism which would detect abusive behavior.
- Consider load balancing as an option to handle heavy loads.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- huntr.com/bounties/788327ec-714a-4d5c-83aa-8df04dd7612bExploit, Third Party Advisory
Other vulnerabilities in mlflow/mlflow
- 8.1 High severity
- 7.7 High severity
- 9.0 Critical severity
- 9.6 Critical severity
- 7.8 High severity
- 8.6 High severity
Recent Insufficient Resource Pool vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.