Advisory

GHSA-3h96-34p3-xm76

Also known as: None

Summary

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

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-05 21:51 UTC
Modified
2026-05-05 22:09 UTC

Affected packages and fixes

graphql

RubyGems · All systems

Affected

  • introduced 2.6.0, fixed 2.6.1 (ecosystem)

Fixed versions

2.6.1

Fix

The export has no generic command for this ecosystem.

graphql

RubyGems · All systems

Affected

  • introduced 2.5.0, fixed 2.5.26 (ecosystem)

Fixed versions

2.5.26

Fix

The export has no generic command for this ecosystem.

graphql

RubyGems · All systems

Affected

  • introduced 2.4.0, fixed 2.4.18 (ecosystem)

Fixed versions

2.4.18

Fix

The export has no generic command for this ecosystem.

graphql

RubyGems · All systems

Affected

  • introduced 2.3.1, fixed 2.3.23 (ecosystem)

Fixed versions

2.3.23

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences