# CVE-2026-100613: capgo.app Authorization Bypass via Stale Channel Permission Overrides

> Former members retain stale channel permissions after app transfer, allowing them to modify destination channels and serve malicious updates to devices.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/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:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-jx6g-vmp7-mvxq

## What is CVE-2026-100613?

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

### Official description

capgo.app is an over-the-air (OTA) update platform for Capacitor apps. In all versions up to and including the current release (no patch available at time of publication), the `transfer_app()` database function transfers an app, its channels, versions and related records to a destination organization without deleting or revalidating existing rows in `channel_permission_overrides`. As a result, a user who legitimately held a channel permission override while a member of the source organization retains that override after the transfer, even though they have no membership and no RBAC binding in the destination organization. Using their own authenticated JWT against the PostgREST API, such a former member can modify the destination-owned channel to point at a different bundle, causing the /updates endpoint to serve an attacker-selected application version to devices. The previously proposed fix for GHSA-626c-p6fq-3whq (PR #3093), which validates organization membership when an override is created or updated, does not remove overrides that became stale as a result of an app transfer.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-100613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100613 is a medium-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 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-100613 exists.

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

## Sources

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

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