How severe is GHSA-3h96-34p3-xm76?

GHSA-3h96-34p3-xm76 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3h96-34p3-xm76?

GHSA-3h96-34p3-xm76 affects the following packages: graphql (RubyGems), graphql (RubyGems), graphql (RubyGems), graphql (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-3h96-34p3-xm76?

Update graphql to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h96-34p3-xm76 is resolved across your whole dependency graph.

How do I detect GHSA-3h96-34p3-xm76 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql. 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.

How do I mitigate GHSA-3h96-34p3-xm76 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-3h96-34p3-xm76?

O3 pinpoints whether GHSA-3h96-34p3-xm76 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3h96-34p3-xm76 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3h96-34p3-xm76 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3h96-34p3-xm76 published, and has it been updated?

GHSA-3h96-34p3-xm76 was published on May 5, 2026 and was last updated on May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

GHSA-3h96-34p3-xm76

MEDIUM

GraphQL-Ruby's Ruby lexer does not count comment tokens for the purposes of max_query_string_tokens

Published

May 5, 2026

Updated

May 5, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

💎graphql💎graphql💎graphql💎graphql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`graphql`	≥ 2.6.0&&< 2.6.1	2.6.1
💎RubyGems	`graphql`	≥ 2.5.0&&< 2.5.26	2.5.26
💎RubyGems	`graphql`	≥ 2.4.0&&< 2.4.18	2.4.18
💎RubyGems	`graphql`	≥ 2.3.1&&< 2.3.23	2.3.23

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql. 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 graphql to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h96-34p3-xm76 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-3h96-34p3-xm76 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-3h96-34p3-xm76. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-3h96-34p3-xm76 in your dependencies?

O3 detects GHSA-3h96-34p3-xm76 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works