CVE-2026-56307: Cap-go capgo · Always-Incorrect Control Flow Implementation
Affects Cap-go capgoSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 12.128.12 when convenient.
Data as of 2 Nov 2026, 10:58 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.
- Patch
- Available – fixed in 12.128.12
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 2 Nov 2026.
What to do
Upgrade Cap-go capgo to 12.128.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cap-gocapgo | Affected
| Fixed in
|
AI-suggested
Since this is a cloud-hosted service, the vendor manages remediation server-side. A patch is available for the underlying software (Cap-go 12.128.12 and later). Users should verify with the vendor advisory that the service has been updated and no further action is required on their part.
Description
Cap-go before 12.128.12 contains a broken cursor pagination vulnerability in the /private/devices endpoint on the Cloudflare/workerd path that allows authenticated attackers to cause duplicate-page loops and make later rows unreachable. Attackers with app.read_devices access can exploit non-advancing cursor filters to trigger infinite pagination loops, prevent dataset traversal, and cause repeated processing in device-management workflows.