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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 7.5 · graphql-pythonNVD modified 2026-10-29 21:38
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/graphql-python/graphql-core/security/advisories/GHSA-mpqx-q82w-9x46 x_refsource_confirm
- https://github.com/graphql-python/graphql-core/issues/287 x_refsource_misc
- https://github.com/graphql-python/graphql-core/pull/288 x_refsource_misc
- https://github.com/graphql-python/graphql-core/commit/3c319fd9f4b8f6c9db4189520561bf8dd0e70be9 x_refsource_misc
- https://github.com/graphql-python/graphql-core/releases/tag/v3.3.1 x_refsource_misc