Service interruption via unbounded batched GraphQL queries
Published Mar 20, 2025 · Updated Oct 15, 2025
Uncontrolled resource consumption in MLflow 2.17.2 allows remote attackers to interrupt service through batched GraphQL queries. The /graphql endpoint accepts large query batches that repeatedly enumerate every run in an experiment without bounding work per request. No authentication or user interaction is required, but exploitation depends on sufficiently expensive queries occupying all available workers.
Summary
What happened
Uncontrolled resource consumption in MLflow 2.17.2 allows remote attackers to interrupt service through batched GraphQL queries. The /graphql endpoint accepts large query batches that repeatedly enumerate every run in an experiment without bounding work per request. No authentication or user interaction is required, but exploitation depends on sufficiently expensive queries occupying all available workers.
The record
- CVE
- CVE-2025-0453
- Published
- Mar 20, 2025
- Updated
- Oct 15, 2025
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-410, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 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.
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- huntr GraphQL batch-query proof of conceptproof of concept · unverified
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