CVE-2026-75508: high-severity vulnerability in graphql-python graphql-core
GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.6%
GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.2.3 until 3.2.12 and 3.3.0rc1, the parser's max_tokens limit in Parser.advance_lexer counts only non-comment tokens returned after Lexer.lookahead skips comments. Each skipped comment is still allocated as a Token and retained through token.next and token.prev, allowing a highly compressible comment-padded GraphQL document to pass a low token limit while consuming memory. An unauthenticated remote attacker can exhaust worker memory before AST-based depth or complexity controls run. This issue is fixed in versions 3.2.12 and 3.3.0rc1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
graphql-python · graphql-coreRelated CVEs — graphql-python graphql-core
In the same product, most dangerous first.
References
https://github.com/graphql-python/graphql-core/commit/437dea102e92fdf05a2971ca76787c5a5bad875ahttps://github.com/graphql-python/graphql-core/commit/80ef435a1808fbbcc4aaac63ae76771a1c91002dhttps://github.com/graphql-python/graphql-core/releases/tag/v3.2.12https://github.com/graphql-python/graphql-core/releases/tag/v3.3.0rc1https://github.com/graphql-python/graphql-core/security/advisories/GHSA-r77w-qph3-7vf8