CVE-2026-75508GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit
Updated under an hour ago ()
Does this affect you?
It affects graphql-python graphql-core. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.57%, higher than 47% of scored CVEs.
Do this next
Free account, 1 product
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
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-400, CWE-770
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.57% (percentile 47)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Oct 22, 2026
- First seen by InfoSec Signals
- Oct 22, 2026
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.