Denial of service in GraphQL-core OverlappingFieldsCanBeMerged rule
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Partial Red Hat: 2 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-400.
Summary
GraphQL-core, a Python port of GraphQL.js, is affected from 3.0.0 before 3.2.12 and from 3.3.0a1 before 3.3.0rc1. The OverlappingFieldsCanBeMerged validation rule repeatedly compares fields that share response names and re-compares flattened inline fragments, causing quadratic and worst-case O(n²·m²) CPU work (CWE-407). An unauthenticated remote attacker can pin a worker process with a crafted query and saturate a multi-worker service, because this work runs before resolver-level depth or complexity controls.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.0.0 until 3.2.12 and 3.3.0rc1, the OverlappingFieldsCanBeMerged rule in specified_rules repeatedly compares fields that share response names and recursively re-compares flattened inline fragments during the validation phase. The prior named-fragment memoization does not cover this path, so nested repeated inline fragments can drive quadratic and worst-case O(n²·m²) CPU work before any resolver or AST-based depth or complexity control runs. An unauthenticated remote attacker can submit a shallow, highly compressible GraphQL query that pins a worker process and can saturate a multi-worker service. This issue is fixed in versions 3.2.12 and 3.3.0rc1.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| graphql-python | graphql-core | 3.0.0 to before 3.2.12; 3.3.0a1 to before 3.3.0rc1 | 3.2.12, 3.3.0rc1 | Patch available | CNA |
| — | graphql-core (PyPI) | 3.0.0 to before 3.2.12 | 3.2.12 | Patch available | GHSA-vj8h-fx38-h3vc |
| — | graphql-core (PyPI) | 3.3.0a1 to before 3.3.0rc1 | 3.3.0rc1 | Patch available | GHSA-vj8h-fx38-h3vc |
- graphql-core Vendorgraphql-python Affected 3.0.0 to before 3.2.12; 3.3.0a1 to before 3.3.0rc1 Fixed in 3.2.12, 3.3.0rc1 Patch available CNA
- graphql-core (PyPI) Vendor— Affected 3.0.0 to before 3.2.12 Fixed in 3.2.12 Patch available GHSA-vj8h-fx38-h3vc
- graphql-core (PyPI) Vendor— Affected 3.3.0a1 to before 3.3.0rc1 Fixed in 3.3.0rc1 Patch available GHSA-vj8h-fx38-h3vc
Remediation
Upgrade graphql-core to 3.2.12 if you run a version from 3.0.0 before 3.2.12, or to 3.3.0rc1 if you run a version from 3.3.0a1 before 3.3.0rc1. Red Hat lists Exploit Intelligence and Red Hat OpenShift AI (RHOAI) as affected without a fix, with no plan available for either.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA graphql-core (graphql-python) Fixed in 3.2.12, 3.3.0rc1
- Fix · GHSA-vj8h-fx38-h3vc graphql-core (PyPI) Fixed in 3.2.12 Advisory →
- Fix · GHSA-vj8h-fx38-h3vc graphql-core (PyPI) Fixed in 3.3.0rc1 Advisory →
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Exploit Intelligence | Affected | No fix yet |
| Red Hat OpenShift AI (RHOAI) | Affected | No fix yet |
Not affected: 1 product
- Red Hat OpenShift AI (RHOAI)
Timeline
- 2026-10-22 Threatist record created from CVE-2026-75507
- 2026-10-22 Alias added: GHSA-vj8h-fx38-h3vc
- 2026-10-22 Fix available: PyPI/[email protected], PyPI/[email protected] · GHSA-vj8h-fx38-h3vc
- 2026-10-22 CVSS score added · GHSA-vj8h-fx38-h3vc
- 2026-10-22 Weakness changed · GHSA-vj8h-fx38-h3vc
- 2026-10-22 6 new references · GHSA-vj8h-fx38-h3vc
- 2026-10-23 Affected versions changed · Red Hat
- 2026-10-23 CVSS score added · Red Hat
- 2026-10-23 Priority changed: MEDIUM → LOW
- 2026-10-23 CISA SSVC decision points changed
- 2026-10-24 Priority changed: LOW → MEDIUM
- 2026-11-06 Affected versions changed · Red Hat
References
Other 6
- https://github.com/graphql-python/graphql-core/security/advisories/GHSA-vj8h-fx38-h3vc
- https://github.com/graphql-python/graphql-core/commit/150e59814d97d12140be005a558c93188ef89198
- https://github.com/graphql-python/graphql-core/commit/29c2753a7ee30a96a4109e7c6add1a2dae0497d7
- https://github.com/graphql-python/graphql-core/releases/tag/v3.2.12
- https://github.com/graphql-python/graphql-core/releases/tag/v3.3.0rc1
- https://github.com/graphql-python/graphql-core
More graphql-python vulnerabilities
- TI-2026-79314 Comment tokens bypass max_tokens limit in graphql-core parser CVSS 3.1HIGH 7.5
- TI-2026-82783 GraphQL-core: Denial of service via memory leak in aborted validations CVSS 3.1HIGH 7.5
Sources
- CVE-2026-75507 · CVE Program
- CVE-2026-75507 · NVD
- FIRST EPSS
- GHSA-vj8h-fx38-h3vc · GitHub Advisory Database · CC BY 4.0
- CVE-2026-75507 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences