CVE-2026-80051
MediumCVSS 5.9Exploitation Probability (EPSS)
Low risk3th percentile - higher than 3% of all known CVEs
Summary
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.
Risk Assessment
The risk includes potential application crashes (stack overflow) and non-compliance with the GraphQL specification, which may lead to unpredictable behavior and potential DoS attacks.
Recommendation
It is recommended to update the graphql-go library to a patched version or manually validate scalar variable types before use.
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-2022-37315High
graphql-go (aka GraphQL for Go) through 0.8.0 has infinite recursion in the type definition parser.
Original NVD description (English source)
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.