# CVE-2026-119286: GraphQL-core: Denial of service via memory leak in aborted validations


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-119286?

CVE-2026-119286 is a high-severity vulnerability in graphql-python graphql-core, published on 29 Oct 2026. 

### Official description

GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.3.0a3 until 3.3.1, validate() reuses a module-level ValidationAbortedError when a document exceeds max_errors. Python appends frames to the reused exception's traceback on every raise, retaining each document, validation context, and error set for the process lifetime. An unauthenticated client can repeatedly submit a small document with more than 100 validation errors to cause unbounded memory growth before query execution, eventually exhausting worker memory without disclosing or modifying data. This issue is fixed in version 3.3.1.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-119286?


## How do I fix CVE-2026-119286?

No fix has been published for CVE-2026-119286 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119286 being exploited?

There is no known exploitation of CVE-2026-119286 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119286 and fix it if it is affected.

What it is: CVE-2026-119286 is a high-severity vulnerability in graphql-python graphql-core, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119286 in the wild and no public exploit code.

Affected product: graphql-python graphql-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119286/ (Markdown: https://insights.sbomify.com/CVE-2026-119286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119286
- OSV: https://osv.dev/vulnerability/CVE-2026-119286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119286/
Summaries are generated and may contain mistakes; the official description above is the record.