Is CVE-2026-56238 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56238 being exploited in the wild.

How severe is CVE-2026-56238?

High severity, with a CVSS score of 7.5, published 12 July 2026.

Is there a fix for CVE-2026-56238?

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-56238 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-56238?

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.

CVE-2026-56238: Capgo information disclosure in Supabase PostgREST global_stats endpoint

CVE-2026-56238 · Severity: high · CVSS 7.5 · Published 2026-07-12

Capgo, a platform for managing app updates, suffered from a security flaw that exposed sensitive business data to the public. An unauthenticated person could access internal financial metrics, including monthly recurring revenue, total revenue, and customer counts across different plan tiers. This information could be used by competitors for business intelligence or by attackers to understand the scale and usage patterns of the platform.

Technologies: Capgo. Vendors: Capgo.

Quick answers

Is CVE-2026-56238 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56238 being exploited in the wild.
How severe is CVE-2026-56238?: High severity, with a CVSS score of 7.5, published 12 July 2026.
Which products and versions are affected?: Capgo before 12.128.2.
Is there a fix for CVE-2026-56238?: 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-56238 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-56238?: 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 'global_stats' endpoint. The 'public.global_stats' table was exposed to the 'anon' role, allowing any remote attacker with the public API key (which is typically embedded in client-side code) to query sensitive data. Exposed metrics include Monthly Recurring Revenue (MRR), total revenue, revenue breakdowns by plan tier, customer counts, and operational telemetry such as device and plugin statistics. The issue was resolved by restricting access to the endpoint and ensuring Row Level Security (RLS) prevents public reads.

Affected products

Capgo Capgo before 12.128.2

Timeline

2026-03-17: advisory: GitHub Security Advisory published
2026-07-12: disclosed: NVD publication date

References

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