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

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

GHSA-pjx7-wx97-6wf8 ↗

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 >= 1.0.1, <= 2.6.14
fixed in 2.6.15
CWE-1333 Inefficient Regular Expression Complexity
ETK-2026-4100Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:gem/graphql
9h 22msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −34h59mwaiting for further signals−9h22m
−24h
−12h
0

description

The graphql Ruby gem can spend excessive resources parsing specially formed query strings because of a regular-expression matching flaw. An attacker who can submit GraphQL queries to an application may be able to degrade service availability; graphql-c_parser may also be affected where it is in use.

mitigation

Upgrade the graphql gem to version 2.6.15. Until upgraded, restrict untrusted GraphQL query submission and apply request limits to reduce exposure.

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
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-09 19:34Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4100",
  "cve_id": null,
  "display_id": "ETK-2026-4100",
  "ghsa_id": "GHSA-pjx7-wx97-6wf8",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Regular-expression denial of service in graphql",
  "summary": "The graphql Ruby gem can spend excessive resources parsing specially formed query strings because of a regular-expression matching flaw. An attacker who can submit GraphQL queries to an application may be able to degrade service availability; graphql-c_parser may also be affected where it is in use.",
  "mitigation": "Upgrade the graphql gem to version 2.6.15. Until upgraded, restrict untrusted GraphQL query submission and apply request limits to reduce exposure.",
  "vendor": "rubygems",
  "product": "rubygems:graphql",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.1, <= 2.6.14"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "2.6.15"
      ],
      "package_name": "graphql",
      "purl": "pkg:gem/graphql"
    }
  ],
  "cwes": [
    1333
  ],
  "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": 11.428716883333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T19:34:34+00:00",
      "days": -1.4579436148842593,
      "is_lower_bound": true,
      "measured_at": "2026-11-11T06:34:00.370189+00:00",
      "url": "https://github.com/rmosolgo/graphql-ruby/security/advisories/GHSA-pjx7-wx97-6wf8"
    }
  }
}

published 2026-11-10 21:26Z
last change 2026-11-11 06:19Z

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.