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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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

Not in CISA KEV

MEDIUM severity

GraphQL-Ruby's Ruby lexer does not count comment tokens for the purposes of max_query_string_tokensGHSA-3h96-34p3-xm76

MEDIUM

GHSA-3h96-34p3-xm76 is a medium-severity (CVSS 5.3) vulnerability in graphql. A fix is available for graphql — see the affected versions and patch details below.

Published

May 5, 2026

Updated

May 5, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of May 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.5.0&&< 2.5.26	2.5.26`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.4.0&&< 2.4.18	2.4.18`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.3.1&&< 2.3.23	2.3.23`bundle update graphql --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

graphql-ruby

3.9/10

Code-Review1/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

May 5, 2026

Identifiers

GHSA-3h96-34p3-xm76

References

Webgithub.com · GHSA 3h96 34p3 xm76 Packagegithub.com · graphql ruby

Related vulnerabilities

This CVE is medium severity; 1 of 1 other CVE affecting graphql is rated as high or higher (top: critical).

CVE-2025-27407

Provenance

Sources

OSV.devFIRST.org (EPSS)

Last verifiedMay 5, 2026

GraphQL-Ruby's Ruby lexer does not count comment tokens for the purposes of max_query_string_tokensGHSA-3h96-34p3-xm76

Real-World Exposure

Description

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

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