CVE-2022-37315
HighCVSS 7.5Exploitation Probability (EPSS)
Elevated risk57th percentile - higher than 57% of all known CVEs
Summary
graphql-go (aka GraphQL for Go) through 0.8.0 has infinite recursion in the type definition parser.
Risk Assessment
Infinite recursion can lead to resource exhaustion (e.g., memory) and denial of service, potentially disrupting applications using this library.
Recommendation
It is recommended to upgrade the graphql-go library to a version newer than 0.8.0 if available, or apply a workaround by limiting the complexity of type definitions.
Other vulnerabilities in graphql-go
See all- CVE-2026-40476High
In versions 15.31.4 and below, the OverlappingFieldsCanBeMerged validation rule in graphql-go performs O(n²) pairwise comparisons of fields sharing the same response name. An attacker can send a query with thousands of repeated identical fields, causing excessive CPU usage during validation.
- CVE-2026-80051Medium
github.com/graphql-go/graphql (GraphQL for Go) through 0.8.1 does not validate that a scalar variable value matches its declared type. The built-in coerceString and coerceBool functions (scalars.go) accept input whose type does not match the declared String, ID, or Boolean scalar instead of raising the request error that the GraphQL specification mandates. In some cases (but not any typical case of JSON sent to a website), a deeply nested value leads to an unrecoverable "fatal error: stack overflow" condition.
Original NVD description (English source)
graphql-go (aka GraphQL for Go) through 0.8.0 has infinite recursion in the type definition parser.