Resource exhaustion in Apollographql Apollo Gateway
CVE-2025-32031
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.006, 49.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Apollographql Apollo Gateway
- Apollographql Federation — versions < 2.10.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (fkie-cad/nvd-json-data-feeds). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/apollographql/federation/security/advisories/GHSA-p2q6-pwh5-m6jr (Vendor Advisory)
- https://github.com/apollographql/federation/pull/3236 (Patch, Issue Tracking)
- https://github.com/apollographql/federation/releases/tag/%40apollo%2Fgateway%402.10.1 (Release Notes)