# CVE-2026-56310: Cap-go - Authorization Bypass in Organization Members Endpoint via API Key Scope Bypass

> Attackers with org-limited API keys can bypass scope restrictions to read sensitive membership data from unauthorized organizations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-q7xv-p34q-v365

## What is CVE-2026-56310?

CVE-2026-56310 is a medium-severity missing authorization vulnerability in Cap-go capgo, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cap-go before 12.128.2 contains an authorization bypass vulnerability in the GET /organization/members endpoint that allows org-limited API keys to bypass limited_to_orgs restrictions. Attackers with org-limited API keys can read membership data including uid, email, image_url, role, and is_tmp from organizations outside their assigned scope.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-56310?


## How do I fix CVE-2026-56310?

No fix has been published for CVE-2026-56310 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56310 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56310 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56310 and fix it if it is affected.

What it is: CVE-2026-56310 is a medium-severity missing authorization vulnerability in Cap-go capgo, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56310 exists.

Affected product: Cap-go capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56310/ (Markdown: https://insights.sbomify.com/CVE-2026-56310/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56310
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56310
- OSV: https://osv.dev/vulnerability/CVE-2026-56310

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56310/
Summaries are generated and may contain mistakes; the official description above is the record.