# CVE-2026-100627: Capgo bundle promotion API channel RBAC deny override bypass

> Attackers with app-level permissions can bypass channel-specific deny rules to promote bundles to restricted channels, modifying channel versions.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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-633x-9x77-77gf, GHSA-w4hm-mr28-xj78

## What is CVE-2026-100627?

CVE-2026-100627 is a high-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 (Cap-go/capgo.app) server backend Supabase functions contain an incorrect authorization flaw in the API-key bundle promotion path. The PUT /bundle endpoint, available to "all" and "write" API keys, dispatches to setChannel, which authorizes with checkPermission(c, 'channel.promote_bundle', { appId: body.app_id }) and omits the request's channel_id. Because the omitted scope field is passed to rbac_check_permission_direct as SQL NULL, and channel-scope override evaluation is gated on p_channel_id IS NOT NULL, per-channel allow/deny overrides are never evaluated. A principal holding app-level channel.promote_bundle (granted by default to the app_developer and app_uploader roles) can therefore promote a bundle to a channel for which an explicit per-channel deny override exists, updating public.channels.version for the supplied channel_id; the target channel is only validated after authorization. The issue is confirmed on main at commit de66fa51e7ff2f50283cc1455c3d80ab3eb0ae43 and likely earlier versions; no patched version is known at the time of publication.

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

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


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

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

## Is CVE-2026-100627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100627 is a high-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-100627 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-100627/ (Markdown: https://insights.sbomify.com/CVE-2026-100627/index.md)
```

## Sources

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

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