GHSA-3j43-9v8v-cp3f Apollo Router Query Validation Vulnerable to Excessive Resource Consumption via Named Fragment Processing

• crates.io apollo-router: < 1.61.2 → fixed in 1.61.2 • crates.io apollo-router: >= 2.0.0-alpha.0, < 2.1.1 → fixed in 2.1.1

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.