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

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

GHSA-492h-6x29-69mq ↗

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.1.0, <= 2.6.15
fixed in 2.6.16
CWE-863 Incorrect Authorization
ETK-2026-4777Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:gem/graphql
cvss7.0ethiack provisional
12h 54msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −28h41mwaiting for further signals−12h54m
−24h
−18h
−6h
0

description

graphql-ruby versions 2.1.0 through 2.6.15 can fail to run an authorization check for an unrelated object in a query. Exploitation requires a schema with a connection whose node type disables scoped-object reauthorization and an attacker able to submit specially formed queries.

mitigation

Upgrade the graphql gem to version 2.6.16 or later. Until upgrading, review schemas for connections that disable scoped-object reauthorization and avoid that setting where possible.

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
9m
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-4777

{
  "etk_id": "ETK-2026-4777",
  "cve_id": null,
  "display_id": "ETK-2026-4777",
  "ghsa_id": "GHSA-492h-6x29-69mq",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Authorization bypass in graphql-ruby query execution",
  "summary": "graphql-ruby versions 2.1.0 through 2.6.15 can fail to run an authorization check for an unrelated object in a query. Exploitation requires a schema with a connection whose node type disables scoped-object reauthorization and an attacker able to submit specially formed queries.",
  "mitigation": "Upgrade the graphql gem to version 2.6.16 or later. Until upgrading, review schemas for connections that disable scoped-object reauthorization and avoid that setting where possible.",
  "vendor": "rubygems",
  "product": "rubygems:graphql",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.1.0, <= 2.6.15"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "2.6.16"
      ],
      "package_name": "graphql",
      "purl": "pkg:gem/graphql"
    }
  ],
  "cwes": [
    863
  ],
  "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": 8.876674516666666,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T15:57:09+00:00",
      "days": -1.1954572410069444,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T20:38:36.554162+00:00",
      "url": "https://github.com/rmosolgo/graphql-ruby/security/advisories/GHSA-492h-6x29-69mq"
    }
  }
}

published 2026-11-18 09:06Z
last change 2026-11-18 20:36Z

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.