CVE Intelligence
High Denial of service

CVE-2026-75508 — GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit

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.

Published Oct 22, 2026 · Updated Oct 22, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.6% (30-day exploitation probability)+7
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.57%
ahead of 47% of scored CVEs · Oct 27, 2026
Affects
Graphql-python
Graphql-core
CVSS base
7.5
High · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Pip Graphql-core: fixed in version 3.2.12 — github.com (GitHub Security Advisories)
  • Pip Graphql-core: fixed in version 3.3.0rc1 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Graphql-python Graphql-core, Pip Graphql-core).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Graphql-python Graphql-core version >= 3.2.3, < 3.2.12version >= 3.3.0a3, < 3.3.0rc1 Vulnerable CVE Program (cve.org) e CISA ADP
Pip Graphql-core ≥ 3.2.3 and < 3.2.12≥ 3.3.0a3 and < 3.3.0rc1 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 security-advisories@github.com via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-400 · Uncontrolled Resource Consumption

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 27, 2026 · 5 reading(s) · max 0.57%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 22, 2026 · GitHub Security Advisories
  • Affected products added · pip/graphql-core
    Oct 22, 2026 · GitHub Security Advisories
  • Source status changed · Published → Deferred
    Oct 22, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 22, 2026
  • CVSS changed · 7.5
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 22, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 22, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 22, 2026 – Oct 22, 2026

References

6 on the record

Elsewhere on this site

Graphql-python
every CVE for this vendor
Denial of service
same class
CWE-400
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-75507 GraphQL-core: Denial of service via quadratic complexity in the OverlappingFieldsCanBeMerged validation rule 5d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-75508 is "GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit", rated High. It affects Graphql-core (Graphql-python); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.57% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.