CVE-2026-119286: GraphQL-core has denial of service via memory leak in aborted validations

Summary

When a validation was aborted because the document contained more errors than allowed by maxerrors (100 by default), validate() raised a single module-level ValidationAbortedError instance. Python appends the frames of every raise to the existing traceback of an exception that is raised again, so every aborted validation extended the traceback of this shared error. That traceback kept the frames, and with them the document, the validation context and all errors of every aborted validation, alive for the lifetime of the process.

Details

Any client can trigger an aborted validation by sending a small document with more than 100 validation errors, e.g. 101 unknown fields. No authentication is required, and since validation runs before execution, depth limiters and complexity analyzers do not prevent it. Each such request permanently retained about 124 KiB on CPython 3.12, without an upper limit, so memory grew with every request until the process was restarted or killed.

GraphQL.js uses a shared error object at the same place, but JavaScript errors capture their stack trace only once when they are created, so it is not affected. GraphQL-core 3.2 creates a new error for each aborted validation and is not affected either.

Proof of concept

python import gc import tracemalloc from graphql import buildschema, parse, validate

schema = buildschema("type Query { a: Int }") document = parse("{ " + " ".join(f"f{i}" for i in range(101)) + " }")

tracemalloc.start() validate(schema, document) gc.collect() base = tracemalloc.gettracedmemory()[0] for in range(200): validate(schema, document) gc.collect() print((tracemalloc.gettracedmemory()[0] - base) // 1024, "KiB")

With GraphQL-core 3.3.0 on CPython 3.12, the retained memory grows from 147 KiB after one call to about 25 MB after 200 calls. With the fix, it stays constant at about 180 KiB.

Impact

Denial of service through memory exhaustion. A few thousand small requests are enough to push a worker past a typical 256 MB or 512 MB container limit and trigger an OOM kill. No data is disclosed or modified.

Patches

Fixed in 3.3.1.

validate() now creates a new ValidationAbortedError for every aborted validation and removes its traceback and exception context before returning it, so that the returned errors do not keep the frames of the validation alive. The module-level validationabortederror instance, which was not exported, has been removed.

Workarounds

If you cannot upgrade, clear the traceback of the shared error after each validation:

python from graphql.validation import validate as validatedocument from graphql.validation.validate import validationabortederror

def validate(args, kwargs): try: return validatedocument(args, kwargs) finally: validationabortederror.traceback = None

Pass this function instead of the original validate where your framework allows it.

Credits

Reported by @riodw. @Fire162 submitted a first fix in #288.