dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56235

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 []).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cap-go before 12.128.2 has an authorization bypass where Supabase PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) are exposed to the public anon role without org membership or permission verification. Using only the public API key (sb_publishable_*), an unauthenticated attacker can query arbitrary org_id values to extract cross-tenant telemetry (MAU, bandwidth, installs, gets), enumerate app IDs, and use an oracle to confirm org existence (valid org returns metrics, invalid returns []). This is an Insecure Direct Object Reference (IDOR) combined with broken access control.

MitigationImplement authorization checks in the affected RPC functions to enforce org membership and permission validation before returning data, or remove these functions from the anon role and require authenticated session context.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Cap-go version
    Inspect package.json, package-lock.json, or run 'npm list cap-go' or equivalent package manager command to retrieve the installed Cap-go version
    Affected if The installed version is lower than 12.128.2 (e.g., 12.128.1, 12.127.x, etc.)
  2. Verify Supabase integration exists
    Check for Supabase configuration in environment variables or config files. Look for environment variables starting with 'NEXT_PUBLIC_SUPABASE_' or 'SUPABASE_' and confirm a public key beginning with 'sb_publishable_' is present
    Affected if Supabase is configured with a sb_publishable_* public key, enabling unauthenticated API access
  3. Inspect RPC function permissions in database
    Connect to the Cap-go PostgreSQL database and query function permissions: SELECT proname, pronamespace::regnamespace FROM pg_proc WHERE proname IN ('get_app_metrics', 'get_global_metrics', 'get_total_metrics'); Then check: SELECT procacl FROM pg_proc WHERE proname IN ('get_app_metrics', 'get_global_metrics', 'get_total_metrics');
    Affected if The 'anon' role or public role appears in the function ACL with EXECUTE permission on any of these three functions
  4. Test unauthenticated function access
    Using the public sb_publishable_* key, make an HTTP POST request to the Supabase REST endpoint '/rest/v1/rpc/function_name' with a JSON body containing an arbitrary org_id value (e.g., {"org_id": "some-org-uuid"})
    Affected if The request returns valid JSON metrics data (containing fields like mau, bandwidth, installs, or gets) instead of an authorization error or empty array for arbitrary org_id values

You are affected if Cap-go version is below 12.128.2 AND Supabase is connected with a public API key AND the anon role has execute permission on get_app_metrics, get_global_metrics, or get_total_metrics, allowing unauthenticated users to query arbitrary org_ids and retrieve cross-tenant telemetry.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authorization checks in the affected RPC functions to enforce org membership and permission validation before returning data, or remove these functions from the anon role and require authenticated session context.

Recommended fix High confidence

capgo version 12.128.2 or later

  1. 1. Identify the current installed version of Cap-go in your environment using your package manager or project dependencies
  2. 2. If the current version is before 12.128.2, upgrade to version 12.128.2 or later
  3. 3. After upgrading, verify that the PostgREST RPC functions (get_app_metrics, get_global_metrics, get_total_metrics) now properly enforce org membership and permission checks
  4. 4. Confirm that the anon role no longer has unrestricted access to cross-tenant metrics data

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56235 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data