Capgo CVE-2026-100617

Requires an authenticated account with app or org ADMIN privileges on the Capgo (capgo.app) instance - this is the primary limiting factor. The attacker must be able to write/insert rows into the channel_permission_overrides mechanism (via admin API/UI). No user interaction from a victim is needed (UI:N), and no non-default configuration is required - the missing membership validation is inherent. Exploitation is bounded by the fact that the actor must already hold administrative authority; the incremental harm is that granted external (non-member) users can then exercise channel permissions such as channel.promote_bundle to push OTA bundles.

This is a genuine authorization flaw (CWE-862) but its real-world priority is moderate, not critical, and the vendor's 8.7 CVSS 4.0 score is generous. The exploitation actor is already an authenticated org/app administrator (PR:L, and arguably PR:H given admin scope), so the flaw does not grant the attacker any new self-capability - it lets a privileged insider extend channel permissions (e.g. channel.promote_bundle) to arbitrary EXTERNAL, non-member user UUIDs. The vendor rates VC:H/VI:H/VA:H against the vulnerable system, but the direct technical impact of THIS flaw is tampering with authorization state; the high-impact consequence (an outsider then pushing OTA JavaScript bundles to app end users) is a downstream/scope-changed effect that requires the granted external user to subsequently act. There is NO EPSS score, NO CISA KEV listing, and NO public POC in the provided data, so there is no evidence of active or imminent exploitation - status is 'no public exploit identified at time of analysis.' The CVSS vector (AV:N/AC:L/PR:L/UI:N) is internally consistent with the description of an authenticated admin issuing API/DB override inserts. Net: real bug worth patching, but insider/admin-gated with no exploitation signals, so it ranks below the unauthenticated Capgo/Flowise ATO issues.

An authenticated org or app administrator (or a compromised admin account) inserts rows into channel_permission_overrides referencing user UUIDs that do not belong to the organization. Because membership is never validated, those external users receive channel-scoped permissions such as channel.promote_bundle, letting an outsider promote/push OTA bundles to the org's applications. No public exploit code is identified, and the action requires existing admin privileges.