cve.bz

CVE-2026-75508 graphql-python graphql-core: Uncontrolled Resource Consumption

7.5 highEPSS 0.6%Fix available

High (7.5) in graphql-python graphql-core. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in graphql-core 3.2.12, 3.3.0rc1.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-75508 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-75508?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-75508?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-75508 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
graphql-python graphql-core>= 3.2.3, < 3.2.12
graphql-python graphql-core>= 3.3.0a3, < 3.3.0rc1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r77w-qph3-7vf8PyPIgraphql-core>=3.2.3 <3.2.123.2.12
GHSA-r77w-qph3-7vf8PyPIgraphql-core>=3.3.0a3 <3.3.0rc13.3.0rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13graphql-coreno fix listedDEBIAN-CVE-2026-75508
Debian14graphql-core3.2.12-1DEBIAN-CVE-2026-75508
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 1 moregraphql-coreno fix listedUBUNTU-CVE-2026-75508
openSUSELeap 16.0python-graphql-core3.2.6-bp160.2.1openSUSE-SU-2026:22258-1
openSUSELeap 16.1python-graphql-core3.2.6-bp161.2.1openSUSE-SU-2026:22319-1
openSUSETumbleweedpython-graphql-core3.3.1-1.1openSUSE-SU-2026:12474-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because unauthenticated remote attackers can exhaust application memory and crash worker processes without requiring elevated privileges. In Red Hat environments such as Red Hat OpenShift AI and backend cloud services, applications handling GraphQL queries fail to account for skipped comment structures when enforcing token thresholds. Because standard complexity and depth validation occurs only after document parsing completes, specially formatted requests can cause service denial before internal safeguards take effect.

ProductPackageStateAdvisory
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch210-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch210-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-rocm64-torch291-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-rocm-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-training-cuda128-torch29-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9Affected
3 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-75508.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON