Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Optimization Bypass

published 2025-04-07 19 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-10287 , GHSA-94hh-jmq8-2fgp

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits: 0; none known

The Apollo Router Core is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. 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. 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. This could lead to excessive resource consumption and denial of service. This has been remediated in apollo-router versions 1.61.2 and 2.1.1.

Patch / fix

fixed in 2 links 2

crates.io apollo-router 1.61.2, 2.1.1
apollographql apollo_router 1.61.2, 2.1.1

github.com/apollographql/router@ab6675a commit
github.com/apollographql/router@bba032e commit

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 19 mo ago (2025-04-08)

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
crates.io	apollo-router	<1.61.2 >=2.0.0-alpha.0, <2.1.1	1.61.2 2.1.1

Affected products

apollographql router

Classification

Weakness

CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary