Quick answers
- Is CVE-2026-100616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100616 being exploited in the wild.
- How severe is CVE-2026-100616?
- Medium severity, with a CVSS score of 5.5, published 26 September 2026.
- Which products and versions are affected?
- Cap-go Capgo.App all versions prior to fix.
- Is there a fix for CVE-2026-100616?
- 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-100616 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-100616?
- 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 authorization bypass in row-level security (RLS) policies: the public.orgs table UPDATE policy permits org.update_settings role to modify the entire row including the internal customer_id column, despite the official API endpoint allowlisting only safe fields. An authenticated org admin without org.update_billing permission can send a direct Supabase PostgREST query to null or corrupt customer_id, breaking billing and plan enforcement that depends on this field.
Affected products
- Cap-go capgo.app all versions prior to fix
Timeline
- 2026-09-26: disclosed: Advisory published
- 2026-09-08: other: GitHub GHSA-qp5h-v7x3-53cq published