ETK-2026-4099Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-wc34-88mf-j95m ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
rubygems:graphql >= 2.0.0, <= 2.6.14
fixed in 2.6.15
CWE-1284 Improper Validation of Specified Quantity in Input
ETK-2026-4099Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:gem/graphql
9h 33msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −35h10mwaiting for further signals−9h33m
−24h
−12h
0

description

The graphql Ruby gem can fail to enforce an application's configured query complexity limit when legacy complexity-cost calculation is in use. A client may submit a query whose processing cost exceeds the intended limit; exploitation requires the application to use the default :legacy calculation mode.

mitigation

Upgrade the graphql gem to version 2.6.15 or later.

fixed in 2.6.15

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-09 19:35Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4099

{
  "etk_id": "ETK-2026-4099",
  "cve_id": null,
  "display_id": "ETK-2026-4099",
  "ghsa_id": "GHSA-wc34-88mf-j95m",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Query complexity limit bypass in graphql Ruby gem",
  "summary": "The graphql Ruby gem can fail to enforce an application's configured query complexity limit when legacy complexity-cost calculation is in use. A client may submit a query whose processing cost exceeds the intended limit; exploitation requires the application to use the default `:legacy` calculation mode.",
  "mitigation": "Upgrade the `graphql` gem to version 2.6.15 or later.",
  "vendor": "rubygems",
  "product": "rubygems:graphql",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0.0, <= 2.6.14"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "2.6.15"
      ],
      "package_name": "graphql",
      "purl": "pkg:gem/graphql"
    }
  ],
  "cwes": [
    1284
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.33080065,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T19:35:41+00:00",
      "days": -1.4653881396527777,
      "is_lower_bound": true,
      "measured_at": "2026-11-11T06:45:50.576895+00:00",
      "url": "https://github.com/rmosolgo/graphql-ruby/security/advisories/GHSA-wc34-88mf-j95m"
    }
  }
}

published 2026-11-10 21:18Z
last change 2026-11-11 06:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.