Capgo bundle promotion API channel RBAC deny override bypass (CVE-2026-100627) | HOL Guard CVE

High · CVSS 7.2CVE-2026-100627

Capgo bundle promotion API channel RBAC deny override bypass

Answer in brief

CVE-2026-100627 records a High severity (CVSS 7.2) vulnerability in Capgo bundle promotion API channel RBAC deny override bypass. The current sources do not mark it as known exploited. Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 26, 2026Updated Sep 26, 2026Source checked Sep 26, 2026First seen by HOL Sep 26, 2026Material review Sep 26, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.2
Exploitation: Not marked as known exploited
Affected software: Not mapped
Fix availability: Not reported

Why this deserves its current priority

CVSS is 7.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 26, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.