CVE-2026-75508

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

GHSA-r77w-qph3-7vf8 ↗EUVD-2026-108225 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+17mkevAttacks confirmed in the real world.
pip:graphql-core >= 3.2.3, < 3.2.12; >= 3.3.0a3, < 3.3.0rc1
fixed in 3.2.12, 3.3.0rc1
ETK-2026-2469Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/graphql-core
50msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0mpublic poc+17mwaiting for further signals+77m
0
+5min
+10min
+15min

description

graphql-core versions before 3.2.12 and 3.3.0rc1 can fail to account for comments when enforcing the parser's token limit. An unauthenticated attacker who can submit GraphQL documents to a service may consume worker memory and cause denial of service, including where a max_tokens limit is configured.

mitigation

Upgrade graphql-core to 3.2.12 or 3.3.0rc1. Until upgrading, enforce a size limit on the decompressed request body before it reaches the GraphQL parser.

fixed in 3.2.12, 3.3.0rc1

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.
2026-10-22 16:10Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+17m
Δ 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-22 16:10Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 16:10Z
    public poc, published 2026-10-22 16:27Z
  3. 2026-10-22 16:10Z

this entry in the feed

GET /api/v1/feed/CVE-2026-75508

{
  "etk_id": "ETK-2026-2469",
  "cve_id": "CVE-2026-75508",
  "display_id": "CVE-2026-75508",
  "ghsa_id": "GHSA-r77w-qph3-7vf8",
  "euvd_id": "EUVD-2026-108225",
  "status": "published",
  "anchor_state": "anchored",
  "title": "graphql-core comment-token limit bypass causes memory exhaustion",
  "summary": "graphql-core versions before 3.2.12 and 3.3.0rc1 can fail to account for comments when enforcing the parser's token limit. An unauthenticated attacker who can submit GraphQL documents to a service may consume worker memory and cause denial of service, including where a max_tokens limit is configured.",
  "mitigation": "Upgrade graphql-core to 3.2.12 or 3.3.0rc1. Until upgrading, enforce a size limit on the decompressed request body before it reaches the GraphQL parser.",
  "vendor": "pip",
  "product": "pip:graphql-core",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.2.3, < 3.2.12"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.2.12"
      ],
      "package_name": "graphql-core",
      "purl": "pkg:pypi/graphql-core"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.3.0a3, < 3.3.0rc1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.3.0rc1"
      ],
      "package_name": "graphql-core",
      "purl": "pkg:pypi/graphql-core"
    }
  ],
  "cwes": null,
  "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.333326166666666,
  "t0_at": "2026-10-22T16:10:17.124000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-22T16:27:14+00:00",
      "days": 0.011769398148148149,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T16:10:17.124000+00:00",
      "url": "https://github.com/advisories/GHSA-r77w-qph3-7vf8"
    },
    "trigger_signal": {
      "at": "2026-10-22T16:10:17.124000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T16:10:17.124000+00:00",
      "url": "https://github.com/advisories/GHSA-r77w-qph3-7vf8"
    }
  }
}

published 2026-10-22 17:19Z
last change 2026-10-22 17:52Z

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.