CVE-2026-100611 Capgo apikey_manager Role Privilege Escalation via Incomplete Role Deny-list

High 7.1 Published Updated

An authenticated apikey_manager can escalate privileges to deploy roles and push arbitrary OTA updates due to incomplete role restrictions.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-100611?

CVE-2026-100611 is a high-severity vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys. When an authenticated user holding only apikey_manager (permissions org.manage_apikeys and org.read) calls POST /apikey with a JWT session, the only checks applied are the org.manage_apikeys permission, a fixed deny-list of assignable role names (APIKEY_MANAGER_DENIED_ASSIGNABLE_ROLES in public/apikey/scope.ts), and a priority-rank comparison in createRoleBindingForPrincipal (private/role_bindings.ts). No check verifies that the caller actually holds the permissions conferred by the role being assigned. Because the deny-list omits the deploy roles app_developer, app_uploader, channel_developer and channel_uploader, and apikey_manager is seeded with priority_rank 78 — higher than those roles' ranks (68, 66, 58, 57) — the rank check also passes. As a result, an apikey_manager who cannot upload bundles or promote channels can mint an API key bound to a deploy role and use it to push arbitrary OTA JavaScript updates to all end users of the organization's apps. As of the advisory publication no patched version was available.

Weakness: CWE-269

Which versions are affected by CVE-2026-100611?

How do I fix CVE-2026-100611?

No fix has been published for CVE-2026-100611 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-100611 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100611 exists.

Sources

Also known as GHSA-2x4j-p4pr-fvp8, GHSA-p4m4-7g3w-gpqw.

Is CVE-2026-100611 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free