Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
async-graphql versions before 7.0.10 are vulnerable to a directive overload issue. The source does not say what request an attacker must send or whether any authentication is needed, but the impact described is that the server may become unresponsive or very slow, with excess CPU and memory use. Upgrade async-graphql to 7.0.10. As a workaround, limit the number of directives allowed on a single field using SchemaBuilder.limit_directives.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0058, the 48th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:20 UTC First seen by agentprime
- 31 Oct 2026, 15:20 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5gc2-7c65-8fq8
- OSV: GHSA-5gc2-7c65-8fq8
- github.com/async-graphql/async-graphql/security/advisories/GHSA-5gc2-7c65-8fq8
- nvd.nist.gov/vuln/detail/CVE-2024-47614
- github.com/async-graphql/async-graphql/commit/7f1791488463d4e9c5adcd543962173e2f6cbd34
- github.com/async-graphql/async-graphql