GHSA-g56x-7j6w-g8r8
HIGHGrackle has StackOverflowError in GraphQL query processing
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.typelevel:grackle-core_2.13☕org.typelevel:grackle-core_3☕org.typelevel:grackle-core_sjs1_2.13☕org.typelevel:grackle-core_sjs1_3☕org.typelevel:grackle-core_native0.4_2.13☕org.typelevel:grackle-core_native0.4_3☕edu.gemini:gsp-graphql-core_2.13☕edu.gemini:gsp-graphql-core_3+4 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.typelevel:grackle-core_2.13 | all versions | 0.18.0 |
| ☕Maven | org.typelevel:grackle-core_3 | all versions | 0.18.0 |
| ☕Maven | org.typelevel:grackle-core_sjs1_2.13 | all versions | 0.18.0 |
| ☕Maven | org.typelevel:grackle-core_sjs1_3 | all versions | 0.18.0 |
| ☕Maven | org.typelevel:grackle-core_native0.4_2.13 | all versions | 0.18.0 |
| ☕Maven | org.typelevel:grackle-core_native0.4_3 | all versions | 0.18.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.typelevel:grackle-core_2.13. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.typelevel:grackle-core_2.13 to 0.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g56x-7j6w-g8r8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-g56x-7j6w-g8r8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-g56x-7j6w-g8r8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g56x-7j6w-g8r8 in your dependencies?
O3 detects GHSA-g56x-7j6w-g8r8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.