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.
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.
Apollo Router's usage of Apollo Compiler has been updated so that validation logic processes each named fragment only once, preventing redundant traversal.
This has been remediated in apollo-router versions 1.61.2 and 2.1.1.
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.
We appreciate the efforts of the security community in identifying and improving the performance and security of query validation mechanisms.
| Score | Percentile |
|---|---|
| 0.53% | 66.90% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 7.5 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-3j43-9v8v-cp3f ↗ |
| CVE | CVE-2025-32380 ↗ |
| CWE id | Name |
|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| rust | apollo-router | < 1.61.2 | 1.61.2 | — |
| rust | apollo-router | >= 2.0.0-alpha.0, < 2.1.1 | 2.1.1 | — |