graphql-go up to 0.8.1 Scalar Coercion scalars.go coerceString/coerceBool stack-based overflow

Summaryinfo

A vulnerability classified as problematic has been found in graphql-go up to 0.8.1. This affects the function coerceString/coerceBool of the file scalars.go of the component Scalar Coercion. The manipulation leads to stack-based overflow. This vulnerability is uniquely identified as CVE-2026-80051. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in graphql-go up to 0.8.1 and classified as problematic. This issue affects the function coerceString/coerceBool of the file scalars.go of the component Scalar Coercion. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-80051 since 08/25/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/25/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• graphql-go

Version

• 0.8.0
• 0.8.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion