Advisory record · GHSA-r77w-qph3-7vf8

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

CVSS 7.5 HighEPSS 0.0057 · 47th percentile

Published by the GitHub Advisory Database at 22 Oct 2026, 16:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
graphql-corePyPI>=3.2.3, <3.2.12 || >=3.3.0a3, <3.3.0rc13.2.12, 3.3.0rc1
Identifiers
GHSA-r77w-qph3-7vf8 · CVE-2026-75508
Weakness (CWE)
CWE-400 · CWE-770
Published
22 Oct 2026
Updated
22 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GraphQL-core versions 3.2.3 before 3.2.12 and 3.3.0a3 before 3.3.0rc1 are vulnerable to denial of service, because the parser's max_tokens limit did not count comment tokens. An unauthenticated attacker can send a comment-padded GraphQL document that passes the limit while still allocating a large number of token objects, which can exhaust memory. Upgrade to 3.2.12 or 3.3.0rc1. Comments now count toward max_tokens, so documents with many comments may need a higher limit.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0057, the 47th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:08 UTC First seen by agentprime
  2. 31 Oct 2026, 14:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.