Quick answers
- Is CVE-2026-100617 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100617 being exploited in the wild.
- How severe is CVE-2026-100617?
- High severity, with a CVSS score of 8.8, published 26 September 2026.
- Which products and versions are affected?
- Cap-go Capgo.App all.
- Is there a fix for CVE-2026-100617?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-100617 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100617?
- 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 channel_permission_overrides table lacks validation that principal IDs belong to the target organization. The RLS INSERT policy only checks if the caller can manage app roles, but does not verify that the principal_id is an organization member, group belongs to the org, or API key is valid. The permission engine subsequently trusts override rows as authoritative, allowing authenticated admins to craft arbitrary overrides with external user UUIDs to grant channel-scoped permissions like channel.promote_bundle.
Affected products
- Cap-go capgo.app all
Timeline
- 2026-09-26: disclosed
- 2026-09-08: advisory: GHSA-626c-p6fq-3whq published