GraphQL-core has denial of service via memory leak in aborted validations

[ Description ]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.

[ Fixes ]Fixes and patches

• graphql-core 3.3.1Fixed version · GitHub Advisories · pip package graphql-core: upgrade to 3.3.1 or later (affected >= 3.3.0a3, < 3.3.1)

[ Packages ]Affected open-source packages

• graphql-core pipAffected >= 3.3.0a3, < 3.3.1 · fixed in 3.3.1 · GHSA-mpqx-q82w-9x46

[ References ]References

• github.com/graphql-python/graphql-core/commit/3c319fd9f4b8f6c9db4189520561bf8dd0e70be9
• github.com/graphql-python/graphql-core/issues/287
• github.com/graphql-python/graphql-core/pull/288
• github.com/graphql-python/graphql-core/releases/tag/v3.3.1
• github.com/graphql-python/graphql-core/security/advisories/GHSA-mpqx-q82w-9x46