CVE-2026-56235: Exposure of Sensitive Information to an Unauthorized Actor in Cap-go capgo
Cap-go capgo before 12.128.2 contains an authorization bypass in several Supabase PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) that are granted to the anon role without enforcing org membership or permission checks. An unauthenticated attacker using only the public Supabase API key (sb_publishable_*) can query arbitrary org_id values to disclose cross-tenant usage telemetry (MAU, bandwidth, installs, gets), enumerate app IDs for a target org, and determine org existence via an oracle (valid org returns metrics, invalid returns []).
AI Analysis
Technical Summary
CVE-2026-56235 describes an authorization bypass in Cap-go capgo before version 12.128.2. The vulnerability affects multiple Supabase PostgREST RPC functions that are exposed to the anon role without enforcing organization membership or permission validation. An attacker can use the public Supabase API key to query arbitrary org_id values, disclosing sensitive cross-tenant telemetry data such as monthly active users, bandwidth, installs, and gets. Additionally, the attacker can enumerate app IDs for a target organization and determine whether an organization exists based on the response pattern of these RPC calls.
Potential Impact
The vulnerability allows unauthorized disclosure of sensitive telemetry data across tenants, including usage metrics and app identifiers. This exposure can lead to privacy violations and information leakage about organizations using the service. However, it does not require authentication or elevated privileges beyond the public API key. There is no indication of direct data modification or service disruption from this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected RPC functions or enforce additional permission checks at the application or API gateway level to prevent unauthorized access. Monitor vendor communications for updates regarding a patch or official remediation.
CVE-2026-56235: Exposure of Sensitive Information to an Unauthorized Actor in Cap-go capgo
Description
Cap-go capgo before 12.128.2 contains an authorization bypass in several Supabase PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) that are granted to the anon role without enforcing org membership or permission checks. An unauthenticated attacker using only the public Supabase API key (sb_publishable_*) can query arbitrary org_id values to disclose cross-tenant usage telemetry (MAU, bandwidth, installs, gets), enumerate app IDs for a target org, and determine org existence via an oracle (valid org returns metrics, invalid returns []).
CVSS v4.0
Score 6.9medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-56235 describes an authorization bypass in Cap-go capgo before version 12.128.2. The vulnerability affects multiple Supabase PostgREST RPC functions that are exposed to the anon role without enforcing organization membership or permission validation. An attacker can use the public Supabase API key to query arbitrary org_id values, disclosing sensitive cross-tenant telemetry data such as monthly active users, bandwidth, installs, and gets. Additionally, the attacker can enumerate app IDs for a target organization and determine whether an organization exists based on the response pattern of these RPC calls.
Potential Impact
The vulnerability allows unauthorized disclosure of sensitive telemetry data across tenants, including usage metrics and app identifiers. This exposure can lead to privacy violations and information leakage about organizations using the service. However, it does not require authentication or elevated privileges beyond the public API key. There is no indication of direct data modification or service disruption from this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected RPC functions or enforce additional permission checks at the application or API gateway level to prevent unauthorized access. Monitor vendor communications for updates regarding a patch or official remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-19T21:50:06.625Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a36bb2a49568db4e2fc696c
Added to database: 06/20/2026, 16:09:14 UTC
Last enriched: 06/27/2026, 21:30:21 UTC
Last updated: 08/04/2026, 12:46:13 UTC
Views: 100
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.