CVE-2025-32034: Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion
Impact
Summary
A vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. This could lead to excessive resource consumption and denial of service.
Details
Named fragments were being expanded once per fragment spread during query planning, leading to exponential resource usage when deeply nested and reused fragments were involved.
Fix/Mitigation
A new Query Fragment Expansion Limit metric has been introduced: - This metric computes the number of selections a query would have if its fragment spreads were fully expanded. - The metric is checked against a limit to prevent excessive computation.
Patches
This has been remediated in apollo-router versions 1.61.2 and 2.1.1.
Workarounds
The only known workaround is "Safelisting" or "Safelisting with IDs only" per Safelisting with Persisted Queries - Apollo GraphQL Docs.
References
Query Planning Documentation
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the performance and security of query planning mechanisms.
Other sources
The Apollo Router Core is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. Prior to 1.61.2 and 2.1.1, a vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. Named fragments were being expanded once per fragment spread during query planning, leading to exponential resource usage when deeply nested and reused fragments were involved. This could lead to excessive resource consumption and denial of service. This has been remediated in apollo-router versions 1.61.2 and 2.1.1.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-32034?
CVE-2025-32034 is considered a medium severity vulnerability in the Apollo Router.
How do I fix CVE-2025-32034?
To fix CVE-2025-32034, upgrade Apollo Router to version 1.61.2 or 2.1.1 and ensure that all configurations are secured.
What versions are affected by CVE-2025-32034?
CVE-2025-32034 affects Apollo Router versions prior to 1.61.2 and 2.1.1.
What type of attacks can exploit CVE-2025-32034?
CVE-2025-32034 can be exploited through queries that use deeply nested and reused named fragments.
Is there a workaround for CVE-2025-32034?
There are no official workarounds for CVE-2025-32034; upgrading is the recommended solution.