# CVE-2026-56314: Capgo - Deleted Bundle Selection via Missing Deletion Filter in /updates Endpoint

> Attackers can deploy deleted application bundles to devices by exploiting missing deletion filters in the update resolution logic.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/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:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-hqq2-87cp-j83x

## What is CVE-2026-56314?

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

### Official description

Capgo before 12.128.12 fails to filter deleted app versions when joining channels during /updates resolution, allowing deleted bundles to remain selectable. Attackers can continue deploying deleted bundles to devices by exploiting the missing app_versions.deleted filter in channel version joins.

Weakness: CWE-672 (Operation on a Resource after Expiration or Release)

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


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

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

## Is CVE-2026-56314 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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