CVE-2026-134795

graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 Denial of Service via Parser max_tokens Comment Runs

Published Nov 22, 2026 CVSS 4.0 · 6.9 Medium EPSS n/a KEV · Not listed
Description
graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 contains a denial of service vulnerability that allows unauthenticated attackers to bypass the parser max_tokens limit using long runs of comments. Attackers can submit GraphQL documents of consecutive comments that Lexer.lookahead fully tokenizes before limit checks, consuming CPU and memory proportional to document size.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to graphql-core version 3.2.14 or later.
  • Upgrade to graphql-core version 3.3.2 or later.
  • Apply server‑side input size limits or reject requests containing excessively large comment blocks to reduce the chance of resource exhaustion.

Generated by OpenCVE AI on November 22, 2026 at 22:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 contains a denial of service vulnerability that allows unauthenticated attackers to bypass the parser max_tokens limit using long runs of comments. Attackers can submit GraphQL documents of consecutive comments that Lexer.lookahead fully tokenizes before limit checks, consuming CPU and memory proportional to document size.
Title graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 Denial of Service via Parser max_tokens Comment Runs
First Time appeared Graphql
Graphql graphql
Weaknesses CWE-770
CPEs cpe:2.3:a:graphql:graphql:*:*:*:*:*:*:*:*
Vendors & Products Graphql
Graphql graphql
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 22, 2026, 9:22 PM
Reserved
Nov 22, 2026, 5:09 PM
Status
Received
Published
Nov 22, 2026, 10:17 PM
Modified
Nov 22, 2026, 10:17 PM