Is CVE-2026-119286 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119286 being exploited in the wild.

How severe is CVE-2026-119286?

High severity, with a CVSS score of 7.5, published 29 October 2026.

Which products and versions are affected?

Graphql-Core 3.3.0a3 to 3.3.1; graphql-core (PyPI) >= 3.3.0a3, < 3.3.1, ECOSYSTEM:introduced=3.3.0a3,fixed=3.3.1.

Is there a fix for CVE-2026-119286?

Yes. graphql-core (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-119286 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-119286?

Check whether you run Graphql-Core or graphql-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119286: GraphQL-core memory leak in validation error handling

Q: Is there a fix for CVE-2026-119286?

Yes. graphql-core (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-119286 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-119286?

Check whether you run Graphql-Core or graphql-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119286 · Severity: high · CVSS 7.5 · Published 2026-10-29

GraphQL-core is a Python library that processes GraphQL queries. When processing a query with excessive validation errors, the library reuses a shared error object that accumulates memory references with each request, causing unbounded memory consumption on servers handling repeated malicious queries. An attacker can exhaust server memory without authentication, leading to denial of service.

Technologies: graphql-core (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-119286 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119286 being exploited in the wild.
How severe is CVE-2026-119286?: High severity, with a CVSS score of 7.5, published 29 October 2026.
Which products and versions are affected?: Graphql-Core 3.3.0a3 to 3.3.1; graphql-core (PyPI) >= 3.3.0a3, < 3.3.1, ECOSYSTEM:introduced=3.3.0a3,fixed=3.3.1.
Is there a fix for CVE-2026-119286?: Yes. graphql-core (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119286 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119286?: Check whether you run Graphql-Core or graphql-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

graphql-core (PyPI): upgrade to 3.3.1 or later
```
pip install "graphql-core>=3.3.1"
```

Technical details

The validate() function in graphql-core 3.3.0–3.3.1 reuses a module-level ValidationAbortedError when a document exceeds max_errors. Python appends exception frames to the reused object's traceback on each raise, retaining references to document data, validation context, and error sets indefinitely. An unauthenticated client can trigger this by submitting queries with more than 100 validation errors, causing ~124 KiB memory retention per request in a long-running process.

Affected products

graphql-core graphql-core 3.3.0a3 to 3.3.1

Identifiers

CVE-2026-119286
GHSA-mpqx-q82w-9x46

Timeline

2026-10-29: disclosed
2026-10-24: other: Issue reported

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.