Quick answers
- Is CVE-2026-100615 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100615 being exploited in the wild.
- How severe is CVE-2026-100615?
- High severity, with a CVSS score of 8.8, published 26 September 2026.
- Which products and versions are affected?
- Cap-go Capgo.App before 12.267.1.
- Is there a fix for CVE-2026-100615?
- A patch was published on 2026-09-26: fixed in version 12.267.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100615 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100615?
- Check whether you run Cap-go Capgo.App at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper privilege management flaw in the API key rotation endpoint (PUT /apikey). The authorization logic checks only whether the caller can manage API keys and whether the target key's organization is manageable, but fails to validate that the caller's role dominates the target key's role. An authenticated attacker with apikey_manager role can enumerate sibling keys belonging to the same user via the GET endpoint, select a higher-privileged org_super_admin key, and rotate it through PUT, receiving the plaintext replacement secret. The affected code is in supabase/functions/_backend/public/apikey/scope.ts and put.ts; fix requires role-dominance validation before rotation.
Affected products
- Cap-go capgo.app before 12.267.1
Timeline
- 2026-09-26: disclosed
- 2026-09-26: patched: fixed in version 12.267.1