Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Decode GraphQL variables with a deserializer that enforces a maximum nesting depth (Go's standard encoding/json does), which mitigates the stack-overflow condition. There is no library-level workaround for the type-confusion condition short of application-side validation of scalar arguments or a custom scalar; upgrading once a fix ships is the durable remedy.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 25 Aug 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 25 Aug 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| First Time appeared |
Graphql-go Project
Graphql-go Project graphql-go |
|
| Weaknesses | CWE-1287 | |
| CPEs | cpe:2.3:a:graphql-go_project:graphql-go:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Graphql-go Project
Graphql-go Project graphql-go |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-08-25T19:22:26.133Z
Reserved: 2026-08-25T17:55:04.047Z
Link: CVE-2026-80051
Updated: 2026-08-25T19:22:16.788Z
Status : Received
Published: 2026-08-25T18:18:07.120
Modified: 2026-08-25T20:17:08.790
Link: CVE-2026-80051
No data.
OpenCVE Enrichment
Updated: 2026-08-25T20:00:06Z