CVE-2026-77226

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

GHSA-mx4r-g275-wg5r ↗EUVD-2026-92791 ↗

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.
Camunda 7 >= 7.24.0, < 7.24.15
fixed in 7.24.15
ETK-2026-686, permanent identifier
15d 06h 40msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Camunda 7 Admin web application versions 7.24.0 through 7.24.14 have a flawed first-run setup authorization check. An unauthenticated attacker may create an administrator account when the camunda-admin group has no direct members, potentially gaining control of the deployment.

mitigation

Upgrade Camunda 7 to version 7.24.15 or later. Until upgrading, ensure the camunda-admin group has a direct member and restrict unauthenticated access to the Admin web application.

fixed in 7.24.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.
0.69%52nd percentile
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 20:26Z
Δ 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-05 20:26Z
    ghsa: trigger signal, started the run
  2. 2026-10-05 20:26Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-686",
  "cve_id": "CVE-2026-77226",
  "display_id": "CVE-2026-77226",
  "ghsa_id": "GHSA-mx4r-g275-wg5r",
  "euvd_id": "EUVD-2026-92791",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Camunda 7 Admin setup",
  "summary": "Camunda 7 Admin web application versions 7.24.0 through 7.24.14 have a flawed first-run setup authorization check. An unauthenticated attacker may create an administrator account when the camunda-admin group has no direct members, potentially gaining control of the deployment.",
  "mitigation": "Upgrade Camunda 7 to version 7.24.15 or later. Until upgrading, ensure the camunda-admin group has a direct member and restrict unauthenticated access to the Admin web application.",
  "vendor": "camunda",
  "product": "Camunda 7",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.24.0, < 7.24.15"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.24.15"
      ],
      "package_name": "Camunda 7",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0069,
  "epss_percentile": 0.5206,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.623110483333335,
  "t0_at": "2026-10-05T20:26:01.427000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T20:26:01.427000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T20:26:01.427000+00:00",
      "url": "https://github.com/advisories/GHSA-mx4r-g275-wg5r"
    }
  }
}

published 2026-10-05 22:38Z
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.