CVE-2026-75507 json
GraphQL-core: Denial of service via quadratic complexity in the OverlappingFieldsCanBeMerged validation rule
published 2mo ago modified 19d ago also EUVD-2026-108226 , GHSA-vj8h-fx38-h3vc
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi graphql-core 3.2.12, 3.3.0rc1
- graphql-core Debian 14 3.2.12-1
debian advisories DEBIAN-CVE-2026-75507
- python-graphql-core openSUSE Leap 16.0 3.2.6-bp160.2.1
- python-graphql-core openSUSE Tumbleweed 3.3.1-1.1
opensuse advisories openSUSE-SU-2026:22258-1openSUSE-SU-2026:12474-1
Is CVE-2026-75507 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-75507 updated cvss 7.5
graphql-core: graphql-core: Denial of Service via nested inline fragments during query validation
-
Red Hat Exploit Intelligence exploit-intelligence/vulnerability-analysis-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-th-torch-cpu-py312-rhel9, rhoai/odh-th-torch-cuda-py312-rhel9, rhoai/odh-th-torch-rocm-py312-rhel9, rhoai/odh-training-cuda128-torch29-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9, +13 moreaffected: no fix available
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9not affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19d ago
Exploit prediction
0.80% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | graphql-core | >=3.0.0, <3.2.12 >=3.3.0a1, <3.3.0rc1 |
3.2.12 3.3.0rc1 |
Affected products
- graphql-python graphql-core
Classification
References
-
github.com
/graphql-python/graphql-core/commit/150e59814d97d12140be005a558c93188ef89198
web
-
github.com
/graphql-python/graphql-core/commit/29c2753a7ee30a96a4109e7c6add1a2dae0497d7
web
-
github.com
/graphql-python/graphql-core/security/advisories/GHSA-vj8h-fx38-h3vc
web, advisory
-
github.com
/graphql-python/graphql-core/releases/tag/v3.2.12
web
-
github.com
/graphql-python/graphql-core/releases/tag/v3.3.0rc1
web
-
github.com
/graphql-python/graphql-core
package
Sources
- CVE List CVE-2026-75507
- GitHub Advisory GHSA-vj8h-fx38-h3vc
- NVD CVE-2026-75507
- Maintainer advisory GHSA-vj8h-fx38-h3vc
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of graphql-python/graphql-core published their own advisory on GitHub. Reviewed sources take precedence over it.