CVE-2026-75508: GraphQL-core · Denial of service via comment tokens bypassing the parser's max_tokens limit
Affects schemathesisSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.26.0 soon.
Data as of 30 Oct 2026, 07:16 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.26.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade schemathesis to 4.26.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewschemathesispkg:brew/schemathesisOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade GraphQL-core to version 4.26.0 or later, where the parser counts comment tokens towards the max_tokens limit, closing the bypass. If upgrading is not immediately possible, apply a request body-size limit on the decompressed request body before parsing to mitigate memory exhaustion risks. Note that after upgrading, comment-heavy documents may require a higher max_tokens limit due to the changed counting behavior.
Description
A denial of service vulnerability in GraphQL-core allows an attacker to bypass the parser's max_tokens limit by padding documents with comment tokens. These comment tokens were not counted against the max_tokens limit, enabling excessive memory allocation and potential exhaustion. The issue is fixed in GraphQL-core version 4.26.0.
References
- github.com/graphql-python/graphql-core/security/advisories/GHSA-r77w-qph3-7vf8 (opens in a new tab)
- github.com/graphql-python/graphql-core/commit/437dea102e92fdf05a2971ca76787c5a5bad875a (opens in a new tab)
- github.com/graphql-python/graphql-core/commit/80ef435a1808fbbcc4aaac63ae76771a1c91002d (opens in a new tab)
- github.com/graphql-python/graphql-core (opens in a new tab)
- github.com/graphql-python/graphql-core/releases/tag/v3.2.12 (opens in a new tab)
- github.com/graphql-python/graphql-core/releases/tag/v3.3.0rc1 (opens in a new tab)