UBUNTU-CVE-2026-75508 (CVE-2026-75508)
Vulnerability from osv_ubuntu – Published: 2026-10-22 17:16 – Updated: 2026-10-28 17:42 – Source websiteGraphQL-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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-graphql-core",
"binary_version": "2.3.2-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "graphql-core",
"purl": "pkg:deb/ubuntu/graphql-core@2.3.2-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.3.2-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-graphql-core",
"binary_version": "3.2.3-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "graphql-core",
"purl": "pkg:deb/ubuntu/graphql-core@3.2.3-2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.2.3-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-graphql-core",
"binary_version": "3.2.11-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "graphql-core",
"purl": "pkg:deb/ubuntu/graphql-core@3.2.11-1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.2.7-1",
"3.2.8-1",
"3.2.11-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-graphql-core",
"binary_version": "3.2.7-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "graphql-core",
"purl": "pkg:deb/ubuntu/graphql-core@3.2.7-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.2.6-1",
"3.2.6-2",
"3.2.7-1"
]
}
],
"aliases": [],
"details": "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\u0027s 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.",
"id": "UBUNTU-CVE-2026-75508",
"modified": "2026-10-28T17:42:49Z",
"published": "2026-10-22T17:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-75508"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75508"
},
{
"type": "REPORT",
"url": "https://github.com/graphql-python/graphql-core/commit/437dea102e92fdf05a2971ca76787c5a5bad875a"
},
{
"type": "REPORT",
"url": "https://github.com/graphql-python/graphql-core/commit/80ef435a1808fbbcc4aaac63ae76771a1c91002d"
},
{
"type": "REPORT",
"url": "https://github.com/graphql-python/graphql-core/releases/tag/v3.2.12"
},
{
"type": "REPORT",
"url": "https://github.com/graphql-python/graphql-core/releases/tag/v3.3.0rc1"
},
{
"type": "REPORT",
"url": "https://github.com/graphql-python/graphql-core/security/advisories/GHSA-r77w-qph3-7vf8"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-75508"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.