dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56226

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 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 exposes the Supabase PostgREST RPC function public.get_orgs_v6(userid uuid), which is SECURITY DEFINER and granted to the anon role, allowing unauthenticated access. Because the function accepts a caller-supplied user UUID without verifying it matches the authenticated user, an attacker using only the public publishable API key can query POST /rest/v1/rpc/get_orgs_v6 with an arbitrary user UUID to retrieve that user's organization membership, roles, subscription/trial metadata, and management_email (PII).

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 · moderate confidence

Capgo before 12.128.2 exposes a Supabase PostgREST RPC function (public.get_orgs_v6) that is SECURITY DEFINER and granted to the anon role. The function accepts a caller-supplied user UUID without verifying it matches the authenticated user, allowing anyone with the public API key to query arbitrary user UUIDs and retrieve sensitive organization membership, roles, subscription metadata, and PII (management_email).

MitigationUpgrade to Capgo version 12.128.2 or later, which should add proper validation to ensure the caller-supplied UUID matches the authenticated user's identity before returning data.

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 Capgo installation and version
    Query your package manager, application metadata, or check the Capgo SDK/version file in your deployment to determine the installed Capgo version. Compare it to the affected range: versions before 12.128.2.
    Affected if The installed Capgo version is lower than 12.128.2
  2. Locate the vulnerable PostgREST function
    Connect to your Supabase database and query the pg_proc system catalog or use psql to list functions in the public schema: SELECT proname FROM pg_proc WHERE proname = 'get_orgs_v6';
    Affected if The function public.get_orgs_v6 exists in your database
  3. Verify function security definition
    Check if the function is defined as SECURITY DEFINER by querying: SELECT prosecurity, prosrc FROM pg_proc WHERE proname = 'get_orgs_v6';
    Affected if The function has prosecurity set to true (SECURITY DEFINER)
  4. Confirm anon role has execute permission
    Check granted permissions on the function: SELECT grantee, privilege_type FROM information_schema.function_privileges WHERE routine_name = 'get_orgs_v6';
    Affected if The anon role or public has EXECUTE privilege on the function
  5. Test unauthenticated access to arbitrary UUIDs
    Using your public Supabase API key, make a POST request to the get_orgs_v6 RPC endpoint with a caller_supplied_user_uuid parameter pointing to a different user ID than the authenticated session.
    Affected if The API returns organization membership, roles, subscription data, or PII for a UUID that does not match the authenticated user

You are affected if your Capgo version is before 12.128.2 AND the public.get_orgs_v6 SECURITY DEFINER function exists with anon role execute permissions, allowing unauthenticated UUID enumeration.

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

Upgrade to Capgo version 12.128.2 or later, which should add proper validation to ensure the caller-supplied UUID matches the authenticated user's identity before returning data.

Recommended fix High confidence

12.128.2 or later

  1. Upgrade Capgo to version 12.128.2 or later to resolve the insecure direct object reference vulnerability
  2. After upgrading, verify that the public.get_orgs_v6 RPC function now properly validates that the user UUID matches the authenticated user before returning organization data
  3. Confirm that unauthenticated or unauthorized requests to POST /rest/v1/rpc/get_orgs_v6 with arbitrary user UUIDs are rejected

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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