# CVE-2026-56310: Cap-go authorization bypass in organization members endpoint

Source: https://junglewise.ai/threats/cve-2026-56310-cap-go-authorization-bypass-in-organization-members-endpoint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-24. Updated: 2026-06-24  
License: CC BY 4.0 with a link back

CVE-2026-56310 · Severity: medium · CVSS 4.3 · Published 2026-06-24

Cap-go, a platform for managing app updates, contained a security flaw where restricted API keys could access data they weren't supposed to see. Specifically, an API key limited to one organization could be used to view member details—such as email addresses and user roles—of other organizations. This could lead to unauthorized data exposure and a breach of privacy between different business accounts using the service.

## Quick answers

**Is CVE-2026-56310 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-56310 being exploited in the wild.

**How severe is CVE-2026-56310?** Medium severity, with a CVSS score of 4.3, published 24 June 2026.

**Which products and versions are affected?** Cap-go capgo < 12.128.2.

**Is there a fix for CVE-2026-56310?** 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-56310 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-56310?** Check whether anything you run is named in the advisory. 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 Cap-go's backend API due to improper enforcement of API key scopes. While the 'GET /organization/members' endpoint performs standard RBAC checks, it fails to validate the 'limited_to_orgs' restriction associated with specific API keys. An authenticated attacker possessing an API key restricted to a specific organization can successfully query the membership data of other organizations they have general access to, bypassing the intended scope limitation. This exposure includes sensitive fields such as user IDs (uid), email addresses, profile image URLs, and roles. The issue was resolved in version 12.128.2 by implementing explicit organization-scope enforcement.

## Affected products

- Cap-go capgo < 12.128.2

## Timeline

- 2026-05-07: advisory: Vendor advisory published on GitHub
- 2026-06-24: disclosed: CVE published and NVD record created

## References

- [https://github.com/Cap-go/capgo/security/advisories/GHSA-q7xv-p34q-v365](https://github.com/Cap-go/capgo/security/advisories/GHSA-q7xv-p34q-v365)
- [https://www.vulncheck.com/advisories/cap-go-authorization-bypass-in-organization-members-endpoint-via-api-key-scope-bypass](https://www.vulncheck.com/advisories/cap-go-authorization-bypass-in-organization-members-endpoint-via-api-key-scope-bypass)