Quick answers
- Is CVE-2026-56284 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56284 being exploited in the wild.
- How severe is CVE-2026-56284?
- Medium severity, with a CVSS score of 5.3, published 8 July 2026.
- Which products and versions are affected?
- Capgo < 12.128.2.
- Is there a fix for CVE-2026-56284?
- 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-56284 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56284?
- Check whether you run Capgo 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
An information disclosure vulnerability exists in Capgo versions prior to 12.128.2 due to improper access control on the Supabase PostgREST RPC function 'public.get_total_metrics(org_id)'. This function was incorrectly accessible to the 'anon' role using only a public 'sb_publishable' key. An unauthenticated remote attacker can send POST requests to the '/rest/v1/rpc/get_total_metrics' endpoint with a valid organization UUID to retrieve sensitive metrics including Monthly Active Users (MAU), bandwidth usage, and installation counts. Additionally, the endpoint acts as an existence oracle, returning an empty array for invalid UUIDs and a populated metrics object for valid ones. The issue was resolved in version 12.128.2 by restricting access to the function.
Affected products
- Capgo capgo < 12.128.2
Timeline
- 2026-03-03: advisory: GitHub Security Advisory published
- 2026-07-08: disclosed: NVD publication date