CVE-2026-56226: Capgo unauthenticated data disclosure in get_orgs_v6 RPC function

CVE-2026-56226 · Severity: high · CVSS 7.5 · Published 2026-07-08

Capgo, a platform for managing app updates, contained a security flaw that allowed unauthorized access to sensitive user and organization data. By using a publicly available API key, an attacker could retrieve private information such as organization memberships, user roles, billing metadata, and management email addresses for any user. This could lead to the exposure of personally identifiable information (PII) and facilitate targeted social engineering or account takeover attempts.

Technologies: Capgo. Vendors: Capgo.

Quick answers

Is CVE-2026-56226 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-56226 being exploited in the wild.
How severe is CVE-2026-56226?
High severity, with a CVSS score of 7.5, published 8 July 2026.
Which products and versions are affected?
Capgo < 12.128.2.
Is there a fix for CVE-2026-56226?
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-56226 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-56226?
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

The vulnerability exists in the Supabase PostgREST RPC function 'public.get_orgs_v6(userid uuid)'. The function was configured as 'SECURITY DEFINER' and granted execution permissions to the 'anon' role, allowing unauthenticated access via the public publishable API key. Because the function failed to validate that the provided 'userid' matched the authenticated user's identity (or required a valid JWT), an attacker could perform an Insecure Direct Object Reference (IDOR) attack. By supplying an arbitrary user UUID to the POST /rest/v1/rpc/get_orgs_v6 endpoint, an attacker can retrieve organization memberships, roles, subscription/trial status, and the 'management_email' field. The issue is addressed 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

References

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