Skip to main content
VulnerabilityPublished

CVE-2026-56226: Cap-go capgo · Information Exposure

Affects Cap-go capgoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 12.128.2 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. 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 20 Nov 2026.

What to do

Upgrade capgo and cap-go/capgo to 12.128.2.

Affected software

ProductAffectedFixed in
Cap-gocapgoAffected
  • <12.128.2
Fixed in
  • 12.128.2
GitHubcap-go/capgopkg:github/cap-go/capgoOther threatsAffected
  • <12.128.2
Fixed in
  • 12.128.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to the vulnerable RPC function if possible or implement additional access controls to verify user identity before allowing queries. Avoid using the public publishable API key in untrusted environments to limit exposure.

Description

Capgo (Cap-go/capgo) before 12.128.2 exposes the Supabase PostgREST RPC function public.get_orgs_v6(userid uuid), which is SECURITY DEFINER and granted to the anon role, allowing unauthenticated access. Because the function accepts a caller-supplied user UUID without verifying it matches the authenticated user, an attacker using only the public publishable API key can query POST /rest/v1/rpc/get_orgs_v6 with an arbitrary user UUID to retrieve that user's organization membership, roles, subscription/trial metadata, and management_email (PII).

References

Community reviews

Loading reviews…