CVE-2026-75508: GraphQL-core is a Python port of the GraphQL.js reference implementation
Affects graphql-coreSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 3.2.12 : patch graphql-core soon.
Data as of 28 Oct 2026, 22:28 UTC
- Patch
- Available – fixed in 3.2.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10graphql-corepkg:deb/ubuntu/graphql-core?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgraphql-corepkg:deb/ubuntu/graphql-core?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSgraphql-corepkg:deb/ubuntu/graphql-core?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSgraphql-corepkg:deb/ubuntu/graphql-core?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-75508 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-75508 (opens in a new tab)
- github.com/graphql-python/graphql-core/commit/437dea102e92fdf05a2971ca76787c5a5bad875a (opens in a new tab)
- github.com/graphql-python/graphql-core/commit/80ef435a1808fbbcc4aaac63ae76771a1c91002d (opens in a new tab)
- github.com/graphql-python/graphql-core/releases/tag/v3.2.12 (opens in a new tab)
- github.com/graphql-python/graphql-core/releases/tag/v3.3.0rc1 (opens in a new tab)
- github.com/graphql-python/graphql-core/security/advisories/GHSA-r77w-qph3-7vf8 (opens in a new tab)