dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56238

HIGH · 7.5 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 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 before 12.128.2 contains an information disclosure vulnerability in the Supabase PostgREST global_stats endpoint that allows unauthenticated attackers to read sensitive financial and operational metrics using only the public apikey. Remote attackers can query the /rest/v1/global_stats endpoint to expose MRR, total revenue, plan-tier revenue breakdown, customer counts, and operational telemetry.

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 has an information disclosure vulnerability where the Supabase PostgREST /rest/v1/global_stats endpoint exposes sensitive financial metrics (MRR, total revenue, plan-tier revenue breakdown) and operational telemetry to unauthenticated attackers who only possess the public API key, bypassing proper authorization controls.

MitigationRestrict access to the global_stats endpoint by implementing proper authentication/authorization checks, validating API key permissions, or limiting the exposure of sensitive financial data. Update to Capgo 12.128.2 or later which contains the fix.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify your Capgo version
    Check the installed Capgo package version by reviewing your package.json file, the node_modules/capgo version, or running a package manager command like `npm list @capgo/node-sdk` or checking your application's dependencies
    Affected if The installed version is earlier than 12.128.2
  2. Locate the Supabase configuration
    Find your Capgo-supabase configuration file or environment variables that contain the Supabase URL and public API key used by your Capgo integration
    Affected if You have a Supabase backend with Capgo storing data and exposing a PostgREST API
  3. Verify global_stats endpoint exposure
    Send a GET request to `https://<your-supabase-project>/rest/v1/global_stats` using only the public API key (no authentication token) and observe whether the response returns financial metrics (MRR, revenue figures, plan-tier breakdowns)
    Affected if The endpoint returns sensitive financial data with just the public API key and no additional authorization
  4. Confirm authorization controls
    Review the Supabase RLS (Row Level Security) policies or API gateway configuration for the global_stats table to determine if any access controls exist beyond the public API key requirement
    Affected if No RLS policies or additional authorization checks are configured on the global_stats table, or the policies permit public read access

You are affected if your Capgo version is earlier than 12.128.2 AND the /rest/v1/global_stats endpoint returns sensitive financial data using only the public API key without proper authorization enforcement.

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

Restrict access to the global_stats endpoint by implementing proper authentication/authorization checks, validating API key permissions, or limiting the exposure of sensitive financial data. Update to Capgo 12.128.2 or later which contains the fix.

Recommended fix High confidence

Capgo 12.128.2

  1. Upgrade Capgo to version 12.128.2 or later to remediate the information disclosure vulnerability
  2. After upgrading, verify that the /rest/v1/global_stats endpoint is properly secured and requires appropriate authentication
  3. Confirm that sensitive financial metrics (MRR, revenue, customer counts) are no longer accessible without proper authorization

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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