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-32380
Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing
Impact
Summary
A vulnerability in Apollo Router's usage of Apollo Compiler allowed queries with deeply nested and reused named fragments to be prohibitively expensive to validate. This could lead to excessive resource consumption and denial of service.
Details
Named fragments were being processed once per fragment spread in some cases during query validation, leading to exponential resource usage when deeply nested and reused fragments were involved.
Fix/Mitigation
Apollo Router's usage of Apollo Compiler has been updated so that validation logic processes each named fragment only once, preventing redundant traversal.
Patches
This has been remediated in apollo-router versions 1.61.2 and 2.1.1.
Workarounds
The only known workaround is "Safelisting with IDs only" per Safelisting with Persisted Queries - Apollo GraphQL Docs. The "Safelisting" security level is not sufficient, since that level allows freeform GraphQL queries to be sent to Apollo Router.
References
Query Planning Documentation
Acknowledgements
We appreciate the efforts of the security community in identifying and improving the performance and security of query validation 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