Allocation of Resources Without Limits or Throttling Affecting graphql-core package, versions [3.2.3,3.2.12)[3.3.0a3,3.3.0rc1)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-GRAPHQLCORE-21433569
- published22 Oct 2026
- disclosed22 Oct 2026
- creditBZHunt
Introduced: 22 Oct 2026
NewCVE-2026-75508 (opens in a new tab)How to fix?
Upgrade graphql-core to version 3.2.12, 3.3.0rc1 or higher.
Overview
graphql-core is a GraphQL implementation for Python, a port of GraphQL.js, the JavaScript reference implementation for GraphQL.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the advance_lexer function in src/graphql/language/parser.py, where comment tokens are allocated as Token objects and chained into the token linked-list but were not counted toward the max_tokens limit. An attacker can submit a comment-padded GraphQL document that bypasses the max_tokens guard, causing unbounded memory allocation - one Token object per comment - until memory is exhausted.