Is CVE-2026-56225 exploited in the wild?

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

How severe is CVE-2026-56225?

High severity, with a CVSS score of 8.3, published 23 June 2026.

Is there a fix for CVE-2026-56225?

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

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

Am I affected by CVE-2026-56225?

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-56225: Capgo authorization bypass in API key management handlers

CVE-2026-56225 · Severity: high · CVSS 8.3 · Published 2026-06-23

Capgo, a platform for managing app updates and deployments, contained a security flaw in how it handles API keys. An attacker with a restricted API key (limited to a specific app) could bypass security boundaries to view, modify, or delete other API keys belonging to the same account. This could lead to unauthorized access to other applications or a complete takeover of the account's management credentials.

Technologies: Capgo. Vendors: Capgo.

Quick answers

Is CVE-2026-56225 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56225 being exploited in the wild.
How severe is CVE-2026-56225?: High severity, with a CVSS score of 8.3, published 23 June 2026.
Which products and versions are affected?: Capgo < 12.128.2.
Is there a fix for CVE-2026-56225?: 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-56225 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-56225?: 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 authorization bypass exists in Capgo's public API key management handlers (GET, PUT, POST, DELETE) due to improper scope validation. While the system checks for organization-level restrictions (limited_to_orgs), it fails to enforce app-level restrictions (limited_to_apps) for keys created with 'mode=all'. A remote attacker with low privileges (possessing an app-scoped API key) can enumerate, update, or delete sibling API keys belonging to the same account but associated with different applications. This allows for privilege escalation and tampering with account-level credentials. The issue is resolved in version 12.128.2.

Affected products

Capgo Capgo < 12.128.2

Timeline

2026-05-07: advisory: GitHub Security Advisory published
2026-06-23: disclosed: NVD publication date

References

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