dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-56219

HIGH · 7.5 CVSS v3.1 Published 2026-06-30
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 8 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 a NULL-auth bypass vulnerability in the public.get_org_user_access_rbac function that allows unauthenticated attackers to retrieve RBAC role bindings and member email addresses. Attackers can exploit improper NULL comparison in the authorization gate to disclose organization membership, roles, and email addresses via the PostgREST RPC endpoint using only a public API key.

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 authentication bypass in the public.get_org_user_access_rbac PostgREST RPC function. The vulnerability stems from improper NULL comparison logic in the authorization gate, allowing attackers with only a public API key to bypass authentication and query the function to extract RBAC role bindings and organization member email addresses.

MitigationUpgrade Capgo to version 12.128.2 or later to patch the NULL comparison authorization flaw. Additionally, review and enforce proper authentication requirements on the get_org_user_access_rbac function to ensure it cannot be accessed with only a public API key.

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 version
    Locate the installed Capgo version number in your deployment (check package.json, container labels, or version endpoint if available)
    Affected if The installed version is earlier than 12.128.2
  2. Confirm vulnerable function exists
    Query the PostgREST metadata or database schema to verify the public.get_org_user_access_rbac RPC function exists in the database
    Affected if The function exists in the public schema and is exposed via PostgREST API
  3. Test authentication bypass with public API key
    Attempt to call the get_org_user_access_rbac endpoint using ONLY a public API key (no session or user token), sending a request such as POST /rpc/get_org_user_access_rbac with organization identifiers
    Affected if The request succeeds and returns RBAC role bindings or member email addresses without requiring user authentication
  4. Verify NULL comparison behavior in authorization
    If possible, inspect the authorization policy or PL/pgSQL logic for the get_org_user_access_rbac function to identify if it performs NULL comparisons on auth variables (check for patterns like 'auth.jwt() IS NULL' or similar conditional logic that may permit unauthenticated access)
    Affected if The authorization logic contains flawed NULL checks that allow bypass when authentication variables are not provided

You are affected if your Capgo installation is version 12.128.2 or earlier AND the get_org_user_access_rbac function can be accessed using only a public API key to retrieve sensitive RBAC and membership data.

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 Capgo to version 12.128.2 or later to patch the NULL comparison authorization flaw. Additionally, review and enforce proper authentication requirements on the get_org_user_access_rbac function to ensure it cannot be accessed with only a public API key.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the current installed version of Capgo by checking the package.json or running the appropriate version command for your Capgo installation
  2. 2. If the current version is earlier than 12.128.2, plan for an upgrade to version 12.128.2 or later
  3. 3. Before upgrading, review the Capgo release notes for version 12.128.2 to understand any changes
  4. 4. Perform the upgrade by following Capgo's standard upgrade procedure (typically via npm install or your deployment method)
  5. 5. After upgrade, verify that the public.get_org_user_access_rbac function now properly rejects NULL authentication contexts
  6. 6. Test that legitimate API key usage still works correctly for authorized users
Caveat Review Capgo release notes for any breaking changes between your current version and 12.128.2; minor version upgrades typically have minimal breaking changes but API behavior changes should be verified

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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