Apollo Gateway Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| apollographql | federation | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-10284 | 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. |
Github GHSA |
GHSA-p2q6-pwh5-m6jr | Apollo Gateway Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.603% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apollographql
Apollographql apollo Gateway |
|
| CPEs | cpe:2.3:a:apollographql:apollo_gateway:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Apollographql
Apollographql apollo Gateway |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apollo Gateway Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|