CVE-2026-119286
GraphQL-core is a Python port of the GraphQL.js reference implementation
- Risk score
- 60/100
- CVSS
- 7.5 v3.1
- Published
- 29 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 erro…
- Affected
- See advisory
- Fix
- Upgrade the product to 3.3.1 or later.
- Exploitation
- No known exploitation
Why it is Amber
- CVSS 7.5 high
- Remotely exploitable without logging in
- On your watchlist: python
References
- https://github.com/graphql-python/graphql-core/commit/3c319fd9f4b8f6c9db4189520561bf8dd0e70be9
- https://github.com/graphql-python/graphql-core/issues/287
- https://github.com/graphql-python/graphql-core/pull/288
- https://github.com/graphql-python/graphql-core/releases/tag/v3.3.1
- https://github.com/graphql-python/graphql-core/security/advisories/GHSA-mpqx-q82w-9x46
Original 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.
Last activity 29 Oct 2026. Patch Forecast updates every hour.