CVE-2026-56235
Received Received - Intake
Authorization Bypass in Cap-go Supabase PostgREST Metrics Functions

Publication date: 2026-06-20

Last updated on: 2026-06-20

Assigner: VulnCheck

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-20
Last Modified
2026-06-20
Generated
2026-06-20
AI Q&A
2026-06-20
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
capgo capgo to 12.128.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-56235 is a medium-severity vulnerability in Cap-go versions before 12.128.2 that involves an authorization bypass in several Supabase PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics). These functions are accessible to the anon role without enforcing organization membership or permission checks.

An unauthenticated attacker using only the public Supabase API key (sb_publishable_*) can exploit this vulnerability to query arbitrary organization IDs and disclose cross-tenant usage telemetry data such as monthly active users (MAU), bandwidth, installs, and gets. The attacker can also enumerate app IDs for a target organization and determine whether an organization exists by using an oracle: valid organizations return metrics, while invalid ones return an empty list.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive organizational data across tenants. An attacker can access usage telemetry data including monthly active users, bandwidth consumption, install counts, and app IDs for any organization without authentication.

Additionally, the vulnerability allows attackers to enumerate organizations by determining their existence through the response behavior of the affected RPC functions. This can lead to privacy violations and potential targeted attacks based on the exposed information.

Detection Guidance

This vulnerability can be detected by attempting to call the affected Supabase PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) using the public Supabase API key (sb_publishable_*) without authentication.

If these functions return usage telemetry data (such as MAU, bandwidth, installs, gets) for arbitrary org_id values without enforcing permission checks, it indicates the presence of the vulnerability.

A possible detection command could be an HTTP request to the Supabase API endpoint invoking one of these RPC functions with different org_id parameters to check if data is returned without authentication.

  • Example curl command to test get_app_metrics RPC function:
  • curl -X POST https://your-supabase-instance/rest/v1/rpc/get_app_metrics -H "apikey: sb_publishable_*" -H "Content-Type: application/json" -d '{"org_id":"some-org-id"}'

If the response returns metrics data for arbitrary org_id values without requiring authentication or proper permission checks, the vulnerability exists.

Mitigation Strategies

The immediate and recommended mitigation step is to upgrade Cap-go to version 12.128.2 or later, where this authorization bypass vulnerability has been patched.

Until the upgrade can be applied, restrict access to the affected RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) to authenticated users with proper permission checks, and avoid exposing these functions to the anon role.

Additionally, monitor API usage for suspicious queries using the public API key that attempt to access metrics for arbitrary org_id values.

Compliance Impact

CVE-2026-56235 allows unauthorized disclosure of sensitive organizational telemetry data across tenants, including usage metrics and app identifiers, without proper authorization checks.

Such unauthorized access to potentially sensitive data could lead to violations of data protection regulations like GDPR or HIPAA, which require strict controls on access to personal or organizational data and mandate protection against unauthorized disclosure.

By enabling cross-tenant data exposure and organization enumeration, this vulnerability increases the risk of non-compliance with these standards, as it undermines confidentiality and access control requirements.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-56235. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart