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

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

GHSA-965v-9v76-5hg2 ↗

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.5.21
fixed in 2.6.12
CWE-863 Incorrect Authorization
ETK-2026-1960Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:gem/graphql
cvss7.0ethiack provisional
2d 18h 57msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −6.4dwaiting for further signals−2.8d
−6d
−4d
−2d
0

description

GraphQL-Ruby graphql gem deployments using Execution::Next may fail to authorize application-specific fields on certain connection edge types. An attacker may access protected data through those fields when the connection uses scoped objects and scoped-object reauthorization is disabled. Schemas without those conditions are not affected.

mitigation

Upgrade the graphql gem to version 2.6.12. Until upgraded, enable scoped-object reauthorization or avoid exposing application-specific fields on affected connection edge types.

fixed in 2.6.12

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
10m
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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-14 19:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1960",
  "cve_id": null,
  "display_id": "ETK-2026-1960",
  "ghsa_id": "GHSA-965v-9v76-5hg2",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Authorization bypass in GraphQL-Ruby connection edge fields",
  "summary": "GraphQL-Ruby graphql gem deployments using Execution::Next may fail to authorize application-specific fields on certain connection edge types. An attacker may access protected data through those fields when the connection uses scoped objects and scoped-object reauthorization is disabled. Schemas without those conditions are not affected.",
  "mitigation": "Upgrade the graphql gem to version 2.6.12. Until upgraded, enable scoped-object reauthorization or avoid exposing application-specific fields on affected connection edge types.",
  "vendor": "rubygems",
  "product": "rubygems:graphql",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=2.5.21"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "2.6.12"
      ],
      "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": 10.32571545,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T19:00:07+00:00",
      "days": -6.410622687048611,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:24.821763+00:00",
      "url": "https://github.com/rmosolgo/graphql-ruby/security/advisories/GHSA-965v-9v76-5hg2"
    }
  }
}

published 2026-10-18 10:40Z
last change 2026-10-21 04:45Z

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.