Vulnerability Description
Apollo Gateway provides utilities for combining multiple GraphQL microservices into a single GraphQL endpoint. Prior to 2.10.1, a vulnerability in Apollo Gateway allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically due to internal optimizations being frequently bypassed. 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 render gateway inoperable. This could lead to excessive resource consumption and denial of service. This has been remediated in @apollo/gateway version 2.10.1.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apollographql | Apollo Gateway | < 2.10.1 |
Related Weaknesses (CWE)
References
- https://github.com/apollographql/federation/pull/3236Issue TrackingPatch
- https://github.com/apollographql/federation/releases/tag/%40apollo%2Fgateway%402Release Notes
- https://github.com/apollographql/federation/security/advisories/GHSA-p2q6-pwh5-mVendor Advisory
FAQ
What is CVE-2025-32031?
CVE-2025-32031 is a vulnerability with a CVSS score of 7.5 (HIGH). Apollo Gateway provides utilities for combining multiple GraphQL microservices into a single GraphQL endpoint. Prior to 2.10.1, a vulnerability in Apollo Gateway allowed queries with deeply nested and...
How severe is CVE-2025-32031?
CVE-2025-32031 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-32031?
Check the references section above for vendor advisories and patch information. Affected products include: Apollographql Apollo Gateway.