Is CVE-2026-56303 exploited in the wild?

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

How severe is CVE-2026-56303?

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

Is there a fix for CVE-2026-56303?

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

It is attacked over the network, in a web application.

Am I affected by CVE-2026-56303?

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-56303: Capgo information disclosure in find_apikey_by_value RPC function

CVE-2026-56303 · Severity: high · CVSS 7.5 · Published 2026-07-11

Capgo, a platform for managing app updates and deployments, contained a security flaw that allowed unauthorized individuals to validate and profile API keys. By exploiting a misconfigured database function, an attacker could confirm if a leaked API key was valid and retrieve sensitive details about its owner, permissions, and expiration. This could lead to unauthorized access to organizational data or the ability to map out a company's internal infrastructure if any API keys were accidentally exposed in logs or code.

Technologies: Capgo. Vendors: Capgo.

Quick answers

Is CVE-2026-56303 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56303 being exploited in the wild.
How severe is CVE-2026-56303?: High severity, with a CVSS score of 7.5, published 11 July 2026.
Which products and versions are affected?: Capgo < 12.128.2.
Is there a fix for CVE-2026-56303?: 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-56303 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-56303?: 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 an incorrectly configured PostgreSQL function, 'public.find_apikey_by_value(text)'. The function was marked as SECURITY DEFINER and granted EXECUTE permissions to the 'anon' role, making it accessible via the Supabase RPC endpoint (/rest/v1/rpc/find_apikey_by_value) without authentication. If an attacker provides a valid API key value, the function returns the full row from the 'public.apikeys' table, exposing metadata such as user_id, mode, organization scoping, and expiration dates. This serves as a validation oracle for leaked keys and allows for the enumeration of internal account relationships. The issue was resolved in version 12.128.2 by restricting function execution.

Affected products

Capgo Capgo < 12.128.2

Timeline

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

References

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