CVE-2025-32032: Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass
Impact Summary A vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. This could lead to excessive resource consumption and denial of service.
Published Apr 7, 2025 · Updated Apr 8, 2025
Affected packages
apollo-router
- Ecosystem
- Rust (crates.io)
- Affected
- < 1.61.2
- Fixed in
- 1.61.2
- Check
cargo tree -i apollo-router
apollo-router
- Ecosystem
- Rust (crates.io)
- Affected
- >= 2.0.0-alpha.0, < 2.1.1
- Fixed in
- 2.1.1
- Check
cargo tree -i apollo-router
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Summary
A vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. This could lead to excessive resource consumption and denial of service.
Details
The query planner includes an optimization that significantly speeds up planning for applicable GraphQL selections. However, queries with deeply nested and reused named fragments can generate many selections where this optimization does not apply, leading to significantly longer planning times. Because the query planner does not enforce a timeout, a small number of such queries can exhaust router's thread pool, rendering it inoperable.
Fix/Mitigation
- A new Query Optimization Limit metric has been added:
- This metric approximates the number of selections that cannot be skipped by the existing optimization.
- The metric is checked against a limit to prevent excessive computation.
Given the complexity of query planning optimizations, we will continue refining these solutions based on real-world performance and accuracy tests.
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
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the performance and security of query planning mechanisms.
References
- https://github.com/apollographql/router/security/advisories/GHSA-94hh-jmq8-2fgp
- https://github.com/apollographql/router/commit/ab6675a63174715ea6ff50881fc957831d4e9564
- https://github.com/apollographql/router/commit/bba032e183b861348a466d3123c7137a1ae18952
- https://nvd.nist.gov/vuln/detail/CVE-2025-32032
- https://github.com/advisories/GHSA-94hh-jmq8-2fgp
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Rust (crates.io) vulnerabilities
All Rust (crates.io) entriesGHSA-hff2-gcpx-8f4p
Apollo Router Core: Browser Bug Enables Bypass of XS-Search Prevention via Read-Only Cross-Site Request Forgery
medium6.3Mar 26, 2026CVE-2025-64173
Apollo Router Affected by an Access Control Bypass on Polymorphic Types
high7.5Nov 6, 2025CVE-2025-64347
Apollo Router Improperly Enforces Renamed Access Control Directives
high7.5Nov 6, 2025CVE-2025-32033
Apollo Router Operation Limits Vulnerable to Bypass via Integer Overflow
high7.5Apr 7, 2025CVE-2025-32034
Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion
high7.5Apr 7, 2025CVE-2025-32380
Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing
high7.5Apr 7, 2025
