CVE-2026-112776

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

GHSA-7rr3-4jcm-x526 ↗EUVD-2026-104582 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
craftcms cms >= 5.0.0, < 5.11.0
fixed in 5.11.0
CWE-863 Incorrect Authorization
ETK-2026-2085Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 05msince last run
1h 23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+29h09m
0
+2h
+4h
+6h
+8h
+10h

description

Craft CMS versions 5.0.0 through 5.10.x can fail to enforce site boundaries for GraphQL mutations. An attacker with a site-scoped GraphQL token may alter content in another site or remove content shared between sites; GraphQL access and a valid scoped token are required.

mitigation

Upgrade the Craft CMS cms package to version 5.11.0 or later. Until upgraded, restrict GraphQL access and revoke or limit site-scoped tokens where feasible.

fixed in 5.11.0

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.
0.30%21st percentile
agent run time
1h 23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 19:10Z
Δ 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-19 19:10Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2085",
  "cve_id": "CVE-2026-112776",
  "display_id": "CVE-2026-112776",
  "ghsa_id": "GHSA-7rr3-4jcm-x526",
  "euvd_id": "EUVD-2026-104582",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site GraphQL authorization bypass in Craft CMS",
  "summary": "Craft CMS versions 5.0.0 through 5.10.x can fail to enforce site boundaries for GraphQL mutations. An attacker with a site-scoped GraphQL token may alter content in another site or remove content shared between sites; GraphQL access and a valid scoped token are required.",
  "mitigation": "Upgrade the Craft CMS `cms` package to version 5.11.0 or later. Until upgraded, restrict GraphQL access and revoke or limit site-scoped tokens where feasible.",
  "vendor": "craftcms",
  "product": "cms",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0, < 5.11.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.11.0"
      ],
      "package_name": "cms",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.003,
  "epss_percentile": 0.2157,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 83.16045838333334,
  "t0_at": "2026-10-19T19:10:53.896000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T19:10:53.896000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T19:10:53.896000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112776"
    }
  }
}

published 2026-10-19 20:19Z
last change 2026-10-21 09:11Z

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.