CVE-2026-56284: Cap-go capgo · Information Exposure
Affects Cap-go capgoSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 12.128.2 when convenient.
Data as of 20 Nov 2026, 17:35 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.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 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 20 Nov 2026.
What to do
Upgrade Cap-go capgo to 12.128.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cap-gocapgo | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to the public sb_publishable_* key and the public.get_total_metrics RPC function if possible. Monitor for unusual POST requests to /rest/v1/rpc/get_total_metrics and consider implementing additional access controls or rate limiting to reduce exposure.
Description
Capgo (Cap-go/capgo) before 12.128.2 contains an information disclosure vulnerability in the Supabase PostgREST RPC function public.get_total_metrics(org_id), which is callable by the anon role using only the public sb_publishable_* key. An unauthenticated attacker can probe organization existence and leak sensitive usage metrics including MAU, bandwidth, and install counts by sending POST requests to /rest/v1/rpc/get_total_metrics with valid organization UUIDs.