Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
GraphQL-core versions 3.2.3 before 3.2.12 and 3.3.0a3 before 3.3.0rc1 are vulnerable to denial of service, because the parser's max_tokens limit did not count comment tokens. An unauthenticated attacker can send a comment-padded GraphQL document that passes the limit while still allocating a large number of token objects, which can exhaust memory. Upgrade to 3.2.12 or 3.3.0rc1. Comments now count toward max_tokens, so documents with many comments may need a higher limit.
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.0057, the 47th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-r77w-qph3-7vf8
- OSV: GHSA-r77w-qph3-7vf8
- github.com/graphql-python/graphql-core/security/advisories/GHSA-r77w-qph3-7vf8
- github.com/graphql-python/graphql-core/commit/437dea102e92fdf05a2971ca76787c5a5bad875a
- github.com/graphql-python/graphql-core/commit/80ef435a1808fbbcc4aaac63ae76771a1c91002d
- github.com/graphql-python/graphql-core
- github.com/graphql-python/graphql-core/releases/tag/v3.2.12
- github.com/graphql-python/graphql-core/releases/tag/v3.3.0rc1