CVE-2026-56320: Capgo · Improper Authorization
Affects CapgoSource GCVE Database
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jun 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 wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Capgo Capgo | Affected
| Fixed in– |
AI-suggested
Since the vulnerability affects versions before 12.128.2, upgrading to version 12.128.2 or later (once available) is recommended if confirmed by the vendor. Until a fix is released, restrict access to the POST /private/create_device endpoint to trusted users only and monitor for suspicious activity related to device creation. Check the vendor advisory for updates on remediation status.
Description
CVE-2026-56320 is an authorization vulnerability in Capgo versions before 12.128.2. The flaw exists in the POST /private/create_device endpoint, which improperly accepts a caller-supplied org_id parameter without verifying that it matches the organization owning the target application. This allows authenticated attackers to create device records for applications belonging to other organizations, bypassing intended authorization boundaries.