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 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/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-q2f9-x4p4-7Vendor Advisory
FAQ
What is CVE-2025-32030?
CVE-2025-32030 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-32030?
CVE-2025-32030 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-32030?
Check the references section above for vendor advisories and patch information. Affected products include: Apollographql Apollo Gateway.