Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-77226 Overview
Camunda 7 contains an incorrect authorization vulnerability [CWE-863] in the Admin web application's first-run setup endpoint. The SetupResource component determines setup availability by counting only direct members of the camunda-admin group. It does not recognize administrators assigned through other authorization mechanisms. An unauthenticated remote attacker can call the setup user-create endpoint when the camunda-admin group is empty but the system is otherwise fully administered. Successful exploitation creates a new administrator account, enabling account takeover, process deployment, and script execution under the engine's service user. The flaw affects Camunda 7.24.0 before 7.24.15.
Critical Impact
Unauthenticated attackers can create administrator accounts and execute arbitrary processes or scripts as the Camunda engine service user.
Affected Products
- Camunda 7.24.0 through 7.24.14
- Camunda Platform 7 Admin web application
- Deployments where the camunda-admin group has no direct members but administrator rights are granted through other means
Discovery Timeline
- 2026-10-05 - CVE-2026-77226 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-77226
Vulnerability Analysis
The vulnerability resides in the SetupResource class of the Camunda Admin web application. This endpoint handles first-run initialization and is designed to be accessible without authentication only when no administrator exists. The availability check queries direct membership of the camunda-admin group instead of enumerating all principals with administrator authorizations. Camunda supports granting administrator rights through individual user authorizations, group assignments, and identity service integrations such as LDAP. When administrators are configured through any of these alternative paths while the camunda-admin group itself remains empty, the setup endpoint incorrectly reports the system as unconfigured. An attacker reaching this endpoint can then invoke the user-create operation to provision an attacker-controlled administrator account.
Root Cause
The root cause is a flawed authorization decision in SetupResource. The component conflates "group membership count" with "administrator presence," violating the principle that authorization checks must evaluate effective permissions rather than a single configuration artifact. This is a classic incorrect authorization pattern tracked under CWE-863.
Attack Vector
The attack requires network access to the Camunda Admin web application. No authentication, credentials, or user interaction are needed. The attacker sends an HTTP request to the setup user-create endpoint and supplies attributes for a new administrator account. After the account is created, the attacker authenticates normally and gains full administrative control. From there, deploying a malicious BPMN process or script task yields code execution in the context of the Camunda engine service user. Technical details are documented in the Codeant research publication and the VulnCheck advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-77226
Indicators of Compromise
- Unexpected HTTP POST requests to the Admin application setup user-create endpoint from unauthenticated sources
- Newly created user accounts with administrator authorizations that do not correspond to a change ticket or operator action
- Deployment of unrecognized BPMN process definitions or script tasks shortly after a suspicious login
- Camunda engine processes spawning shell interpreters, scripting runtimes, or outbound network connections
Detection Strategies
- Audit the Camunda identity service for membership of the camunda-admin group and compare against users holding administrator authorizations through other paths
- Alert on any invocation of the SetupResource setup endpoint in production, which should never occur after initial provisioning
- Correlate new user creation events with subsequent process deployments or script task executions
Monitoring Recommendations
- Forward Camunda application and web server logs to a centralized analytics platform for retention and query
- Monitor the Java process hosting the Camunda engine for child process creation and unexpected file writes
- Track authentication events for newly created administrator accounts and flag first-use from unusual source addresses
How to Mitigate CVE-2026-77226
Immediate Actions Required
- Upgrade Camunda 7 to version 7.24.15 or later as published through Camunda enterprise distribution channels
- Enumerate all administrator accounts and remove any that cannot be attributed to a legitimate operator
- Ensure at least one direct member exists in the camunda-admin group so the setup logic reports the system as configured
- Restrict network exposure of the Admin web application to trusted management networks
Patch Information
Camunda addressed the issue in release 7.24.15. The fix corrects SetupResource so that setup availability is determined by evaluating all effective administrator authorizations rather than only direct membership of the camunda-admin group. Operators running affected 7.24.x builds should plan an immediate upgrade.
Workarounds
- Add a dedicated service account as a direct member of the camunda-admin group to force the setup endpoint to report the system as initialized
- Block requests to the Admin application setup endpoint at a reverse proxy or web application firewall until patching is complete
- Place the Camunda Admin interface behind an authenticated gateway or VPN to prevent unauthenticated network access
# Example reverse proxy rule to block the setup endpoint (nginx)
location ~* /camunda/api/admin/setup/ {
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

