apollo-router
Affected
- introduced
0, fixed1.61.2(semver)
Fixed versions
1.61.2
Fix
- Fixed version
1.61.2cargo update -p apollo-router --precise 1.61.2
Advisory
Also known as: CVE-2025-32034
Apollo Router Query Planner Vulnerable to Excessive Resource Consumption via Named Fragment Expansion
Impact
Summary
A vulnerability in Apollo Router allowed queries with deeply nested and reused named fragments to be prohibitively expensive to query plan, specifically during named fragment expansion. This could lead to excessive resource consumption and denial of service.
Details
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.
Fix/Mitigation
A new Query Fragment Expansion Limit metric has been introduced:
Patches
This has been remediated in apollo-router versions 1.61.2 and 2.1.1.
Workarounds
The only known workaround is "Safelisting" or "Safelisting with IDs only" per Safelisting with Persisted Queries - Apollo GraphQL Docs.
References
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the performance and security of query planning mechanisms.
High Basis: The source's own band: HIGH
0, fixed 1.61.2 (semver)1.61.2
1.61.2cargo update -p apollo-router --precise 1.61.22.0.0-alpha.0, fixed 2.1.1 (semver)2.1.1
2.1.1cargo update -p apollo-router --precise 2.1.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0