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-100611 Overview
CVE-2026-100611 is a privilege escalation vulnerability in Capgo (capgo.app backend) affecting versions ≤ 12.261.0. The flaw allows an authenticated user holding only the apikey_manager organization role to mint API keys bound to deploy roles the user does not possess. The root cause is an incomplete deny-list (APIKEY_MANAGER_DENIED_ASSIGNABLE_ROLES in public/apikey/scope.ts) combined with a priority_rank comparison that favors apikey_manager. An attacker exploiting this flaw can push arbitrary over-the-air (OTA) JavaScript updates to all end users of the organization's applications. The vulnerability is classified under [CWE-269: Improper Privilege Management]. No patched version was available at the time of advisory publication.
Critical Impact
An apikey_manager with no deploy permissions can mint API keys bound to deploy roles and distribute arbitrary OTA JavaScript payloads to every end user of the organization's mobile applications.
Affected Products
- Capgo capgo.app backend versions ≤ 12.261.0
- Organizations relying on the apikey_manager role for delegated API key administration
- End-user mobile applications receiving OTA updates through affected Capgo deployments
Discovery Timeline
- 2026-09-26 - CVE-2026-100611 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-100611
Vulnerability Analysis
The vulnerability resides in the API key creation path exposed through POST /apikey. When an authenticated user calls this endpoint with a JWT session, the backend performs only three validations: it confirms the caller holds the org.manage_apikeys permission, it checks the requested role against a fixed deny-list, and it compares the caller's priority_rank against the target role's rank in createRoleBindingForPrincipal (private/role_bindings.ts). The backend never verifies that the caller actually holds the permissions conferred by the role being assigned. This design treats role assignment as a hierarchical operation rather than a permission-bounded delegation. The apikey_manager role nominally grants only org.manage_apikeys and org.read, but the incomplete controls elevate it into a de facto super-admin for deploy operations.
Root Cause
The deny-list in public/apikey/scope.ts omits the four deploy roles: app_developer, app_uploader, channel_developer, and channel_uploader. The apikey_manager role is seeded with priority_rank 78, which exceeds the deploy roles' ranks of 68, 66, 58, and 57 respectively. Both guardrails therefore pass for assignments the role should not be able to make.
Attack Vector
An attacker authenticates to the Capgo backend with an apikey_manager session, then issues POST /apikey requesting an API key bound to app_uploader or channel_developer. The returned API key can then be used against the OTA pipeline to upload bundles and promote them to production channels. Because Capgo pushes JavaScript bundles directly to installed applications, the attacker gains code execution within every end-user app in the organization. See the GitHub Security Advisory GHSA-2x4j-p4pr-fvp8 and the VulnCheck Privilege Escalation Advisory for implementation specifics.
Detection Methods for CVE-2026-100611
Indicators of Compromise
- API key creation events where the caller holds only apikey_manager but the created key is bound to app_developer, app_uploader, channel_developer, or channel_uploader.
- OTA bundle uploads or channel promotions authenticated with API keys that were minted by principals lacking deploy permissions.
- Unexpected JavaScript bundle versions appearing on production channels outside of normal release windows.
Detection Strategies
- Audit the apikey table and backend logs for POST /apikey requests that bind deploy roles to keys owned by apikey_manager principals.
- Correlate API key issuance events with subsequent bundle upload and channel promotion activity to identify role-permission mismatches.
- Review historical role bindings created via createRoleBindingForPrincipal for assignments where the caller's non-apikey permissions did not include those of the target role.
Monitoring Recommendations
- Alert on any new API key whose bound role grants permissions the issuing principal does not directly hold.
- Monitor OTA release channels for bundle hashes and versions that did not originate from the organization's CI/CD pipeline.
- Track administrative role changes affecting apikey_manager membership and investigate recent additions.
How to Mitigate CVE-2026-100611
Immediate Actions Required
- Review all accounts assigned the apikey_manager role and revoke the role from any principal that does not require it.
- Enumerate existing API keys and revoke any key bound to a deploy role whose creator does not hold the corresponding deploy permissions.
- Rotate OTA signing credentials and audit recent bundle releases for unauthorized JavaScript payloads.
Patch Information
As of the advisory publication, no patched version was available. Monitor the GitHub Security Advisory GHSA-2x4j-p4pr-fvp8 for upstream fixes. The upstream remediation requires extending APIKEY_MANAGER_DENIED_ASSIGNABLE_ROLES to include every deploy role and adding a permission-subset check inside createRoleBindingForPrincipal so a caller cannot bind permissions it does not hold.
Workarounds
- Temporarily remove the apikey_manager role from all non-administrator accounts and centralize API key issuance with trusted administrators who already hold deploy permissions.
- Enforce out-of-band approval for any new API key bound to app_developer, app_uploader, channel_developer, or channel_uploader roles.
- Restrict backend access to the POST /apikey endpoint at the network layer so only vetted operator IPs can issue new keys.
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

