All reports
High

Grackle has StackOverflowError in GraphQL query processing

Affected versions

Affected versions
<= 0.14.0
Fixed version
Not reported
Affected versions
<= 0.14.0
Fixed version
Not reported
Affected versions
<= 0.14.0
Fixed version
Not reported
Affected versions
<= 0.14.0
Fixed version
Not reported
Affected versions
<= 0.14.0
Fixed version
Not reported
Affected versions
<= 0.14.0
Fixed version
Not reported
Affected versions
< 0.18.0
Fixed version
0.18.0
Affected versions
< 0.18.0
Fixed version
0.18.0
Affected versions
< 0.18.0
Fixed version
0.18.0
Affected versions
< 0.18.0
Fixed version
0.18.0
Affected versions
< 0.18.0
Fixed version
0.18.0
Affected versions
< 0.18.0
Fixed version
0.18.0

Exploitation

CVE-2023-50730

Probability of exploitation in the next 30 days: 0.83%

FIRST EPSS · 2026-11-21

Description

Impact

Prior to this fix, the GraphQL query parsing was vulnerable to StackOverflowErrors. The possibility of small queries resulting in stack overflow is a potential denial of service vulnerability.

This potentially affects all applications using Grackle which have untrusted users.

[!CAUTION]
No specific knowledge of an application's GraphQL schema would be required to construct a pathological query.

Patches

The stack overflow issues have been resolved in the v0.18.0 release of Grackle.

Workarounds

Users could interpose a sanitizing layer in between untrusted input and Grackle query processing.

Links