Skip to main content

CVE-2026-75508: CWE-400: Uncontrolled Resource Consumption in graphql-python graphql-core

0
High
VulnerabilityCVE-2026-75508cvecve-2026-75508cwe-400cwe-770
Published: 10/22/2026 (10/22/2026, 16:10:17 UTC)
Source: CVE Database V5
Vendor/Project: graphql-python
Product: graphql-core

Description

A vulnerability in graphql-core, a Python GraphQL implementation, allows unauthenticated remote attackers to cause uncontrolled resource consumption. The parser's max_tokens limit does not properly account for comment tokens, which are retained in memory despite being skipped, enabling memory exhaustion before other controls activate. This issue affects versions from 3.2.3 up to but not including 3.2.12, and from 3.3.0a3 up to but not including 3.3.0rc1. The vulnerability has a high severity with a CVSS score of 7.5 and is fixed in versions 3.2.12 and 3.3.0rc1.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected software

graphql-python

graphql-core

Affected versions
>=3.2.3 <3.2.12>=3.3.0a3 <3.3.0rc1
graphql-core
pkg:pypi/graphql-core
Affected versions
>=3.2.3 <3.2.12>=3.3.0a3 <3.3.0rc1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/22/2026, 16:45:17 UTC

Technical Analysis

GraphQL-core versions 3.2.3 through 3.2.11 and 3.3.0a3 through 3.3.0rc1 contain a vulnerability (CVE-2026-75508) where the parser's max_tokens limit counts only non-comment tokens after skipping comments, but comment tokens are still allocated and linked in memory. This allows an attacker to craft a GraphQL document padded with many compressible comments that bypass the token limit while consuming excessive memory. This uncontrolled resource consumption can exhaust worker memory before AST-based depth or complexity controls are applied. The issue is resolved in versions 3.2.12 and 3.3.0rc1.

Potential Impact

An unauthenticated remote attacker can exploit this vulnerability to exhaust server memory resources, potentially leading to denial of service conditions. There is no impact on confidentiality or integrity, but availability is severely affected due to memory exhaustion.

Mitigation Recommendations

Upgrade graphql-core to version 3.2.12 or later, or to 3.3.0rc1 or later, where the issue is fixed. No other mitigations are specified or required once patched.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-08-17T20:49:21.598Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ada3a444d27ba8daa66741e

Added to database: 10/22/2026, 16:31:00 UTC

Last enriched: 10/22/2026, 16:45:17 UTC

Last updated: 10/22/2026, 16:46:07 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses