CVE-2026-88860: Cap-go capgo.app · Incorrect Authorization
Affects Cap-go capgo.appSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 10/25/2026, 16:58:58 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wild: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cap-gocapgo.app | Affected
| Fixed in– |
AI-suggested
Until a fix is available, carefully review and manually audit channel permission overrides when revoking user roles to ensure no stale permissions remain.
Description
Capgo fails to clean up channel permission overrides when a user's last organization role binding is deleted, leaving stale overrides active. Attackers can retain channel-specific permissions after their base RBAC access has been revoked to perform unauthorized actions like changing production OTA versions.
Impact
Attackers can retain elevated channel-specific permissions after their general role-based access control (RBAC) permissions are revoked. This enables unauthorized actions such as changing production OTA versions, potentially leading to unauthorized code deployment or system compromise. The vulnerability severely impacts confidentiality, integrity, and availability of the affected system.