Is CVE-2026-56230 exploited in the wild?

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

How severe is CVE-2026-56230?

High severity, with a CVSS score of 8.8, published 30 June 2026.

Is there a fix for CVE-2026-56230?

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

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

Am I affected by CVE-2026-56230?

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-56230: Capgo BOLA in middlewareKey via x-limited-key-id header

CVE-2026-56230 · Severity: high · CVSS 8.8 · Published 2026-06-30

Capgo, a platform for managing app updates and deployments, contained a security flaw that allowed users of one organization to access data belonging to another. By providing a specific identification number in a web request, an authenticated user could trick the system into granting them the permissions of a different customer. This could lead to the unauthorized viewing or modification of sensitive application data and organizational resources across the platform.

Technologies: Capgo. Vendors: Capgo.

Quick answers

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

A Broken Object Level Authorization (BOLA) vulnerability exists in the `middlewareKey()` function within `supabase/functions/_backend/utils/hono_middleware.ts`. The middleware accepts a client-controlled `x-limited-key-id` header and resolves the associated subkey without verifying that the subkey belongs to the authenticated user's organization. While other code paths like `foundAPIKey()` perform this check, `middlewareKey()` fails to call `validateSubkeyUser()`. An attacker with a valid API key can exploit this by supplying a target tenant's subkey ID, effectively adopting that tenant's authorization context. This grants unauthorized access to various API endpoints, including those for apps, bundles, channels, and organizations. The issue is resolved in version 12.128.2.

Affected products

Capgo Capgo < 12.128.2

Timeline

2026-02-10: advisory: GitHub Security Advisory published
2026-06-30: disclosed: NVD publication date

References

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