# CVE-2026-56293: Capgo - Stale Cross-Organization Authorization via Incomplete deploy_history Update in transfer_app()

> Attackers can retain unauthorized access to deployment history or cause data loss during app transfers due to incomplete ownership updates.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-854w-xj7g-prv3, GHSA-9ph8-2cv6-679j

## What is CVE-2026-56293?

CVE-2026-56293 is a medium-severity missing authorization vulnerability in Capgo, published on 8 Jul 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 transfer_app() that fails to update deploy_history.owner_org when transferring applications between organizations. Attackers can exploit this omission to retain unauthorized access to deployment history records in the source organization or cause the destination organization to lose access to transferred application deployment records.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-56293 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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