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

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

GHSA-wqwf-8p4q-mwqj ↗

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.3.0, <= 2.6.15
fixed in 2.6.16
CWE-407 Inefficient Algorithmic Complexity
ETK-2026-4776Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:gem/graphql
cvss7.0ethiack provisional
12h 49msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+17h05m
0
+6h
+12h
+24h
+30h

description

The graphql RubyGems package is affected when query complexity limiting is enabled. A remote client able to submit specially structured valid GraphQL queries may cause excessive CPU consumption during complexity analysis, outside the normal validation timeout.

mitigation

Upgrade the graphql gem to version 2.6.16 or later. Until the upgrade is deployed, restrict untrusted access to GraphQL query endpoints and monitor them for abnormal CPU use.

fixed in 2.6.16

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
11m
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-17 15:57Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4776",
  "cve_id": null,
  "display_id": "ETK-2026-4776",
  "ghsa_id": "GHSA-wqwf-8p4q-mwqj",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Exponential-time complexity analysis in graphql",
  "summary": "The `graphql` RubyGems package is affected when query complexity limiting is enabled. A remote client able to submit specially structured valid GraphQL queries may cause excessive CPU consumption during complexity analysis, outside the normal validation timeout.",
  "mitigation": "Upgrade the `graphql` gem to version 2.6.16 or later. Until the upgrade is deployed, restrict untrusted access to GraphQL query endpoints and monitor them for abnormal CPU use.",
  "vendor": "rubygems",
  "product": "rubygems:graphql",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.3.0, <= 2.6.15"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "2.6.16"
      ],
      "package_name": "graphql",
      "purl": "pkg:gem/graphql"
    }
  ],
  "cwes": [
    407
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.2196267,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T15:57:03+00:00",
      "days": -1.2455521532175926,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:50:38.772472+00:00",
      "url": "https://github.com/rmosolgo/graphql-ruby/security/advisories/GHSA-wqwf-8p4q-mwqj"
    }
  }
}

published 2026-11-18 08:55Z
last change 2026-11-18 21:43Z

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.