Technical impact
The vulnerability lies in the parser’s token limit enforcement mechanism. An attacker can send a GraphQL document composed entirely of long comment runs, which the lexer processes fully before the max_tokens check is applied. This results in excessive CPU consumption and memory usage proportional to the size of the document, ultimately causing the application to become unresponsive. The weakness is characterized by CWE-770, which relates to Resource Exhaustion.
Affected Systems
Affected versions of the graphql-core library include all releases from 3.2.12 up to, but not including, 3.2.14, and all releases from 3.3.0rc1 up to, but not including, 3.3.2. The product is provided by the vendor graphql-python.
Risk and Exploitability
The CVSS base score is 6.9, indicating moderate severity. No EPSS value is available, and the vulnerability is not listed in the CISA KEV catalog, implying no widespread, publicly known exploits. Because the vulnerability allows bypass of the token limit through unauthenticated requests, the attack vector is likely remote: any client that can transmit raw GraphQL queries to the target server can trigger the denial of service. Attacks would require only the ability to send a specially crafted payload, with no authentication required.