CVE-2026-56226: Exposure of Sensitive Information to an Unauthorized Actor in Cap-go capgo
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).
AI Analysis
Technical Summary
The vulnerability in Capgo (before version 12.128.2) involves the Supabase PostgREST RPC function public.get_orgs_v6(userid uuid), which is SECURITY DEFINER and accessible by the anon role, enabling unauthenticated access. The function accepts a user UUID parameter without verifying that it corresponds to the authenticated user, allowing an attacker with only the public publishable API key to invoke POST /rest/v1/rpc/get_orgs_v6 with arbitrary UUIDs. This leads to unauthorized disclosure of sensitive information including organization membership, roles, subscription and trial metadata, and personally identifiable information such as management_email.
Potential Impact
An attacker can retrieve sensitive user information without authentication by exploiting the exposed RPC function. This includes organization membership details, user roles, subscription and trial metadata, and personally identifiable information (PII) such as management_email. The exposure of this data can lead to privacy violations and potential further targeted attacks. The vulnerability has a high severity rating (CVSS 8.7) due to its ease of exploitation and the sensitivity of the data exposed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is indicated, users should monitor the vendor's communications for updates. Until a fix is available, 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.
CVE-2026-56226: Exposure of Sensitive Information to an Unauthorized Actor in Cap-go capgo
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).
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Capgo (before version 12.128.2) involves the Supabase PostgREST RPC function public.get_orgs_v6(userid uuid), which is SECURITY DEFINER and accessible by the anon role, enabling unauthenticated access. The function accepts a user UUID parameter without verifying that it corresponds to the authenticated user, allowing an attacker with only the public publishable API key to invoke POST /rest/v1/rpc/get_orgs_v6 with arbitrary UUIDs. This leads to unauthorized disclosure of sensitive information including organization membership, roles, subscription and trial metadata, and personally identifiable information such as management_email.
Potential Impact
An attacker can retrieve sensitive user information without authentication by exploiting the exposed RPC function. This includes organization membership details, user roles, subscription and trial metadata, and personally identifiable information (PII) such as management_email. The exposure of this data can lead to privacy violations and potential further targeted attacks. The vulnerability has a high severity rating (CVSS 8.7) due to its ease of exploitation and the sensitivity of the data exposed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is indicated, users should monitor the vendor's communications for updates. Until a fix is available, 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-19T21:46:58.630Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4e5b32c9d9e3dbe33e52d5
Added to database: 07/08/2026, 14:14:10 UTC
Last enriched: 07/08/2026, 14:28:20 UTC
Last updated: 08/22/2026, 08:08:25 UTC
Views: 90
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.