CVE-2026-119286: graphql-core · Uncontrolled Resource Consumption
Affects graphql-coreSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.3.1 soon.
Data as of 29 Oct 2026, 21:59 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 3.3.1
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 29 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 graphql-core to 3.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| graphql-pythongraphql-core | Affected
| Fixed in
|
PyPIgraphql-corepkg:pypi/graphql-coreOther 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 3.3.1 or later, where this issue is fixed. No other mitigation is required as the vulnerability is addressed by this official fix.
Description
A vulnerability in graphql-core versions from 3.3.0a3 up to but not including 3.3.1 allows unauthenticated clients to cause uncontrolled memory growth by repeatedly submitting documents with more than 100 validation errors. This occurs because the validate() function reuses a module-level exception, causing tracebacks to accumulate and retain memory indefinitely. The issue is fixed in version 3.3.1.
References
- github.com/graphql-python/graphql-core/security/advisories/GHSA-mpqx-q82w-9x46 (opens in a new tab)
- github.com/graphql-python/graphql-core/issues/287 (opens in a new tab)
- github.com/graphql-python/graphql-core/pull/288 (opens in a new tab)
- github.com/graphql-python/graphql-core/commit/3c319fd9f4b8f6c9db4189520561bf8dd0e70be9 (opens in a new tab)
- github.com/graphql-python/graphql-core/releases/tag/v3.3.1 (opens in a new tab)