Summary
CVE-2026-77226 is a critical incorrect-authorization vulnerability (CWE-863) affecting the Admin web application of Camunda 7. The flaw resides in the SetupResource first-run setup endpoint, which miscalculates whether an administrator already exists in the system, allowing an unauthenticated remote attacker to create a new administrator account under certain conditions. The issue carries a CVSS v4.0 base score of 9.2 (Critical) and can lead to full account takeover.
Technical details
- Root cause:
SetupResourcedetermines whether initial setup is still "available" by checking only the direct membership count of the specialcamunda-admingroup, rather than recognizing all administrators actually configured in the system (e.g., via identity-provider integrations, group-based authorization, or other admin configuration paths). - Trigger condition: If the
camunda-admingroup is empty — which can occur after certain identity-provider syncs, migrations, or configuration states even though the engine is otherwise fully administered — the setup flow incorrectly treats the installation as "not yet set up." - Attack vector: Network, unauthenticated, no user interaction required. An attacker who can reach the Admin web application’s setup endpoint sends a request to the setup user-creation API to register a brand-new administrator account.
- Impact: Creation of an attacker-controlled administrator account results in account takeover of the Camunda Admin application, and can be leveraged to deploy malicious processes or execute scripts with the privileges of the engine’s service user — affecting confidentiality, integrity, and availability.
Affected software
- Camunda 7, versions 7.24.0 up to (but not including) 7.24.15
Severity
- CVSS v4.0 Base Score: 9.2 (Critical) —
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CVSS v3.1 Base Score: 8.1 (High) —
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade Camunda 7 to version 7.24.15 or later, where the setup-availability check has been corrected.
- If immediate patching is not possible:
- Ensure the
camunda-admingroup is never left empty; verify at least one user is always a direct member of this group, even when administrators are managed through an external identity provider or other authorization configuration. - Consider configuring a static/plugin-based administrator (e.g., via administrator authorization configuration) so the setup flow does not rely solely on
camunda-admingroup membership. - Restrict network access to the Camunda Admin web application (e.g., via firewall rules, VPN, or reverse proxy allow-listing) so the setup endpoint is not reachable from untrusted networks.
- Monitor for unexpected administrator account creation events and audit existing admin accounts for unauthorized additions.
- Ensure the

