dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56284

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-08
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 6 weeks old

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
Capgo (Cap-go/capgo) before 12.128.2 contains an information disclosure vulnerability in the Supabase PostgREST RPC function public.get_total_metrics(org_id), which is callable by the anon role using only the public sb_publishable_* key. An unauthenticated attacker can probe organization existence and leak sensitive usage metrics including MAU, bandwidth, and install counts by sending POST requests to /rest/v1/rpc/get_total_metrics with valid organization UUIDs.

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

Capgo before version 12.128.2 exposes a Supabase PostgREST RPC function (public.get_total_metrics) that is accessible to the anonymous role using only the public sb_publishable_* API key. This allows unauthenticated attackers to retrieve sensitive organization usage metrics (MAU, bandwidth, install counts) by sending POST requests with valid organization UUIDs to /rest/v1/rpc/get_total_metrics.

MitigationUpdate Capgo to version 12.128.2 or later to patch the vulnerability. Additionally, restrict the RPC function to require proper authentication and authorization checks instead of being accessible via the public anon role.

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 Capgo installed version
    Locate the Capgo package.json or check the running application version. Compare against 12.128.2.
    Affected if Version is below 12.128.2
  2. Identify Supabase configuration
    Locate Capgo configuration files or environment variables for Supabase connection details. Look for sb_publishable_* API keys.
    Affected if sb_publishable_* public API key is configured and in use
  3. Verify RPC function existence
    Query the Supabase database for the presence of public.get_total_metrics function: SELECT proname FROM pg_proc WHERE proname = 'get_total_metrics';
    Affected if The public.get_total_metrics function exists in the database
  4. Check anonymous role permissions
    Query PostgreSQL permissions on the function: SELECT procacl FROM pg_proc WHERE proname = 'get_total_metrics'; Verify if the anon role or public has EXECUTE permission.
    Affected if The anon role or public has EXECUTE permission on get_total_metrics
  5. Test unauthenticated access
    Send a POST request to /rest/v1/rpc/get_total_metrics with a valid organization UUID in the request body, using only the sb_publishable_* key in the Authorization header.
    Affected if The request succeeds and returns organization metrics without authentication

You are affected if Capgo is version below 12.128.2 AND the public.get_total_metrics RPC function is callable by the anonymous role using the public API key.

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

Update Capgo to version 12.128.2 or later to patch the vulnerability. Additionally, restrict the RPC function to require proper authentication and authorization checks instead of being accessible via the public anon role.

Recommended fix High confidence

12.128.2

  1. Identify the current Capgo installation version in use
  2. Upgrade Capgo to version 12.128.2 or later release
  3. After upgrading, verify the fix by confirming the public.get_total_metrics RPC function no longer returns sensitive metrics to the anon role
  4. If self-hosting Capgo, ensure the sb_publishable_* key is not being used as the sole authentication method for sensitive RPC calls

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56284 — 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-56284 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