Skip to main content
← All vulnerabilities
CVE-2026-75508GHSA-R77W-QPH3-7VF8EUVD-2026-108225

GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 3.2.12, 3.3.0rc1
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: yes
  • Technical impact: partial

Summary

The GraphQL-core Python library, a port of the GraphQL.js reference implementation, is affected, and the flaw lets an unauthenticated remote attacker send a specially crafted, comment-heavy GraphQL document that slips past the parser's token limit and consumes large amounts of server memory, potentially crashing the worker processing requests.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original 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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • graphql-python graphql-core

    From 3.2.3 · fixed in 3.2.12; From 3.3.0a3 · fixed in 3.3.0rc1

  • graphql-corePyPI

    From 3.2.3 · fixed in 3.2.12

  • graphql-corePyPI

    From 3.3.0a3 · fixed in 3.3.0rc1

References 5

GitHub · graphql-python/graphql-core