{"answers":{"affected":"8 open source packages ship an affected version, including graphql.","exploited":"There is no known exploitation of GHSA-3h96-34p3-xm76 in the wild and no public exploit code.","fix":"Upgrade graphql to a fixed version for your release line: 2.3.23, 2.4.18, 2.5.26 or 2.6.1.","what":"GHSA-3h96-34p3-xm76 is a denial of service vulnerability in graphql, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-3h96-34p3-xm76 and fix it if it is affected.\n\nWhat it is: GHSA-3h96-34p3-xm76 is a denial of service vulnerability in graphql, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-3h96-34p3-xm76 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- graphql (RubyGems): affected from 2.3.1; fixed in 2.3.23\n- graphql (RubyGems): affected from 2.3.1; fixed in 2.3.23\n- graphql (RubyGems): affected from 2.4.0; fixed in 2.4.18\n- graphql (RubyGems): affected from 2.4.0; fixed in 2.4.18\n- graphql (RubyGems): affected from 2.5.0; fixed in 2.5.26\n- graphql (RubyGems): affected from 2.5.0; fixed in 2.5.26\n- graphql (RubyGems): affected from 2.6.0; fixed in 2.6.1\n- graphql (RubyGems): affected from 2.6.0; fixed in 2.6.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-3h96-34p3-xm76/ (Markdown: https://insights.sbomify.com/GHSA-3h96-34p3-xm76/index.md)","id":"GHSA-3h96-34p3-xm76","markdown":"https://insights.sbomify.com/GHSA-3h96-34p3-xm76/index.md","name":"GHSA-3h96-34p3-xm76","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby GraphQL library","requires_auth":"none","summary":"Attackers can bypass token limits in GraphQL-Ruby by using comments, potentially causing denial of service if max_query_string_tokens is configured.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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. \n\nIn patched versions, the Ruby lexer does count these tokens. \n\nGraphQL-CParser is not affected by this problem. \n\n`max_query_string_tokens` was introduced in v2.3.1. Each 2.x version has received a new patch release for including a fix.","ecosystems":["RubyGems"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"GraphQL-Ruby's Ruby lexer does not count comment tokens for the purposes of max_query_string_tokens","id":"GHSA-3h96-34p3-xm76","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":8,"n_references":null,"packages":[{"ecosystem":"RubyGems","fixed":["2.3.23"],"introduced":["2.3.1"],"last_affected":[],"package":"graphql","purl":null,"source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.3.23"],"introduced":["2.3.1"],"last_affected":[],"package":"graphql","purl":"pkg:gem/graphql","source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.4.18"],"introduced":["2.4.0"],"last_affected":[],"package":"graphql","purl":null,"source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.4.18"],"introduced":["2.4.0"],"last_affected":[],"package":"graphql","purl":"pkg:gem/graphql","source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.5.26"],"introduced":["2.5.0"],"last_affected":[],"package":"graphql","purl":null,"source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.5.26"],"introduced":["2.5.0"],"last_affected":[],"package":"graphql","purl":"pkg:gem/graphql","source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.6.1"],"introduced":["2.6.0"],"last_affected":[],"package":"graphql","purl":null,"source":"GHSA-3h96-34p3-xm76"},{"ecosystem":"RubyGems","fixed":["2.6.1"],"introduced":["2.6.0"],"last_affected":[],"package":"graphql","purl":"pkg:gem/graphql","source":"GHSA-3h96-34p3-xm76"}],"products":null,"published":"2026-05-05","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass token limits in GraphQL-Ruby by using comments, potentially causing denial of service if max_query_string_tokens is configured.","url":"https://insights.sbomify.com/GHSA-3h96-34p3-xm76/"}