Search
Search Results (3 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2022-37315 | 1 Graphql-go Project | 1 Graphql-go | 2026-08-25 | 7.5 High |
| graphql-go (aka GraphQL for Go) through 0.8.0 has infinite recursion in the type definition parser. | ||||
| CVE-2026-80051 | 1 Graphql-go Project | 1 Graphql-go | 2026-08-25 | N/A |
| 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. | ||||
| CVE-2022-21708 | 2 Graphql-go Project, Redhat | 2 Graphql-go, Openshift | 2025-04-23 | 6.5 Medium |
| graphql-go is a GraphQL server with a focus on ease of use. In versions prior to 1.3.0 there exists a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. The issue has been patched in version `v1.3.0`. The only known workaround for this issue is to disable the `graphql.MaxDepth` option from your schema which is not recommended. | ||||
Page 1 of 1.