Homepage

Resource Exhaustion Affecting graphql-core package, versions <3.2.12-1

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.57% (47th percentile)

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 applications
  • Snyk IDSNYK-DEBIANUNSTABLE-GRAPHQLCORE-21479304
  • published23 Oct 2026
  • disclosed22 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 22 Oct 2026

NewCVE-2026-75508  (opens in a new tab)
CWE-400  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Debian:unstable graphql-core to version 3.2.12-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream graphql-core package and not the graphql-core package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.