# CVE-2026-56222: Capgo - Cross-Organization App Takeover via Mismatched org_id and app_id in /private/role_bindings

> Administrators in one organization can bypass authorization checks to read and modify applications owned by other organizations via the role bindings API.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-5r52-m8r9-7f8x, GHSA-whmp-h7x8-7x69

## What is CVE-2026-56222?

CVE-2026-56222 is a high-severity missing authorization vulnerability in Capgo, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Capgo before 12.128.2 contains an authorization bypass vulnerability in POST /private/role_bindings that fails to verify app_id ownership during app-scoped role binding creation. An attacker with administrative privileges in one organization can create role bindings targeting applications owned by other organizations, enabling unauthorized read and modification of victim applications.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-56222 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56222 is a high-severity missing authorization vulnerability in Capgo, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56222 exists.

Affected product: 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-56222/ (Markdown: https://insights.sbomify.com/CVE-2026-56222/index.md)
```

## Sources

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

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