dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56300

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 unauthenticated security definer RPC functions get_user_id and get_org_perm_for_apikey that expose API key validity oracles and user UUID disclosure. Unauthenticated attackers using the public API key can validate leaked keys, enumerate users and apps, and determine permission levels, significantly increasing the actionability of compromised credentials.

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 contains two unauthenticated SECURITY DEFINER RPC functions (get_user_id and get_org_perm_for_apikey) that expose API key validity oracles and allow user UUID disclosure. Attackers with the public API key can validate leaked/stolen keys, enumerate users and applications, and determine permission levels without authentication.

MitigationUpgrade Capgo to version 12.128.2 or later to remove or properly secure these RPC functions, and immediately rotate any API keys that may have been compromised.

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 installed Capgo version
    Query the Capgo application or database for the current version number (often found in app metadata, environment variables, or a versions table)
    Affected if Version is lower than 12.128.2
  2. Locate the get_user_id RPC function
    Query the database schema for user-defined RPC functions named 'get_user_id' (e.g., SELECT proname FROM pg_proc WHERE proname = 'get_user_id' in PostgreSQL-based deployments)
    Affected if The function exists in the database
  3. Locate the get_org_perm_for_apikey RPC function
    Query the database schema for user-defined RPC functions named 'get_org_perm_for_apikey'
    Affected if The function exists in the database
  4. Verify function security definition
    Inspect the security definition of these RPC functions (look for SECURITY DEFINER attribute in function metadata)
    Affected if The functions are defined with SECURITY DEFINER and no authentication wrapper
  5. Test unauthenticated access to RPC functions
    Attempt to call these RPC functions using the public API key without providing additional authentication credentials
    Affected if The functions return valid responses (user UUIDs, API key validation results, or permission data) without authentication

If Capgo version is below 12.128.2 AND the get_user_id/get_org_perm_for_apikey RPC functions exist as SECURITY DEFINER functions accessible without authentication, the environment is vulnerable to CVE-2026-56300.

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 remove or properly secure these RPC functions, and immediately rotate any API keys that may have been compromised.

Recommended fix High confidence

Capgo version 12.128.2 or later

  1. 1. Identify all Capgo installations in the environment
  2. 2. Check the current version of each Capgo installation
  3. 3. If version is below 12.128.2, plan and schedule an upgrade to version 12.128.2 or later
  4. 4. After upgrading, verify that the security definer RPC functions get_user_id and get_org_perm_for_apikey are no longer accessible without authentication
  5. 5. Review API key logs for any signs of exploitation prior to the upgrade

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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