| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-r77w-qph3-7vf8 | GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 29 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 23 Oct 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Graphql-python
Graphql-python graphql-core |
|
| Vendors & Products |
Graphql-python
Graphql-python graphql-core |
|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 22 Oct 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit | |
| Weaknesses | CWE-400 CWE-770 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-29T11:47:15.190Z
Reserved: 2026-08-17T20:49:21.598Z
Link: CVE-2026-75508
Updated: 2026-10-29T11:47:00.802Z
Status : Deferred
Published: 2026-10-22T17:16:59.933
Modified: 2026-10-29T12:17:13.617
Link: CVE-2026-75508
OpenCVE Enrichment
Updated: 2026-10-22T21:19:12Z
Github GHSA