CVE-2026-56235: Cap-go capgo authorization bypass in Supabase RPC functions

CVE-2026-56235 · Severity: medium · CVSS 5.3 · Published 2026-06-20

Cap-go, a platform for managing app updates, contained a security flaw where sensitive usage data was accessible to unauthorized users. An attacker could use a public API key to view private business metrics such as monthly active users, bandwidth usage, and installation counts for any organization on the platform. This could lead to the exposure of competitive business intelligence and the identification of valid customer accounts.

Quick answers

Is CVE-2026-56235 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-56235 being exploited in the wild.
How severe is CVE-2026-56235?
Medium severity, with a CVSS score of 5.3, published 20 June 2026.
Which products and versions are affected?
Cap-go capgo < 12.128.2.
Is there a fix for CVE-2026-56235?
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-56235 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-56235?
Check whether anything you run is named in the advisory. 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 authorization bypass exists in Cap-go's Supabase PostgREST RPC functions, specifically get_app_metrics, get_global_metrics, and get_total_metrics. These functions were granted to the 'anon' role without implementing internal checks for organization membership or specific permissions. By providing a public Supabase publishable API key and a target organization ID, an unauthenticated attacker can retrieve telemetry data including MAU, bandwidth, and app IDs. The vulnerability also acts as an account oracle, as valid organization IDs return data while invalid ones return an empty array. The issue is resolved in version 12.128.2.

Affected products

  • Cap-go capgo < 12.128.2

Timeline

  • 2026-03-17: advisory: Vendor advisory published on GitHub
  • 2026-06-20: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.