GHSA-3H96-34P3-XM76

GraphQL-Ruby's max_query_string_tokens configuration didn't count comment tokens against the limit, allowing strings to be processed even after the configured maximum had actually been reached.

In patched versions, the Ruby lexer does count these tokens.

GraphQL-CParser is not affected by this problem.

max_query_string_tokens was introduced in v2.3.1. Each 2.x version has received a new patch release for including a fix.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

GHSA-3H96-34P3-XM76 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.6.1, 2.5.26, 2.4.18, 2.3.23); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-3H96-34P3-XM76? GHSA-3H96-34P3-XM76 is a medium-severity allocation of resources without limits or throttling vulnerability in graphql (rubygems), affecting versions = 2.6.0. It is fixed in 2.6.1, 2.5.26, 2.4.18, 2.3.23. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is GHSA-3H96-34P3-XM76? GHSA-3H96-34P3-XM76 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of graphql are affected by GHSA-3H96-34P3-XM76? graphql (rubygems) versions = 2.6.0 is affected.
4. Is there a fix for GHSA-3H96-34P3-XM76? Yes. GHSA-3H96-34P3-XM76 is fixed in 2.6.1, 2.5.26, 2.4.18, 2.3.23. Upgrade to this version or later.
5. Is GHSA-3H96-34P3-XM76 exploitable, and should I be worried? Whether GHSA-3H96-34P3-XM76 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-3H96-34P3-XM76 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-3H96-34P3-XM76?
   • Upgrade graphql to 2.6.1 or later
   • Upgrade graphql to 2.5.26 or later
   • Upgrade graphql to 2.4.18 or later
   • Upgrade graphql to 2.3.23 or later