# CVE-2026-56320: Capgo - Org/App Scope Mismatch in Device Creation Endpoint

> Authenticated attackers can create device records for foreign organizations by bypassing authorization checks in the device creation endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/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:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-mhrc-qhq8-872f, GHSA-r9p9-p57v-w538

## What is CVE-2026-56320?

CVE-2026-56320 is a high-severity missing authorization vulnerability in Capgo, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Capgo before 12.128.2 contains an authorization flaw in POST /private/create_device that accepts a caller-supplied org_id parameter without validating it matches the target app's owner organization. Authenticated attackers can create device records for an application using a foreign organization identifier, bypassing the intended org/app authorization boundary.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-56320 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56320 is a high-severity missing authorization vulnerability in Capgo, published on 30 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-56320 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-56320/ (Markdown: https://insights.sbomify.com/CVE-2026-56320/index.md)
```

## Sources

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

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