Skip to main content
VulnerabilityPublished

CVE-2026-119286: graphql-core · Uncontrolled Resource Consumption

Affects graphql-coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.3.1 soon.

Data as of 29 Oct 2026, 21:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
graphql-pythongraphql-coreAffected
  • >=3.3.0a3 <3.3.1
Fixed in
  • 3.3.1
PyPIgraphql-corepkg:pypi/graphql-coreOther threatsAffected
  • <3.3.1 >=3.3.0a3
Fixed in
  • 3.3.1

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

Community reviews

Loading reviews…