dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56242

HIGH · 7.5 CVSS v3.1 Published 2026-06-21
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

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 unauthenticated security definer RPC function get_identity_apikey_only that returns the owning user_id for supplied API keys, creating an API key validity oracle and user identity disclosure primitive. Attackers can call this endpoint with valid or invalid API keys to confirm key validity and map keys to user identifiers, then chain results into other exposed RPCs like get_orgs_v6 to retrieve organization membership 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 · high confidence

Capgo before 12.128.2 contains an unauthenticated security definer RPC function 'get_identity_apikey_only' that returns the owning user_id for supplied API keys. This creates an API key validity oracle allowing attackers to confirm key validity and map keys to user identifiers, which can then be chained with other exposed RPCs like 'get_orgs_v6' to retrieve organization membership and email PII.

MitigationUpgrade to Capgo version 12.128.2 or later. Additionally, ensure the RPC function requires proper authentication and does not expose user identity information without authorization.

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
    Locate the Capgo installation and determine the installed version by checking package.json, Gemfile, or the running application's version endpoint if available. Compare against the affected range: versions before 12.128.2.
    Affected if The installed version is Capgo and is lower than 12.128.2
  2. Locate the PostgreSQL database used by Capgo
    Access the PostgreSQL database configuration for the Capgo application. This is typically found in database.yml for Rails apps or environment variables (DATABASE_URL). Connect to the database.
    Affected if Capgo uses a PostgreSQL database and the application is vulnerable
  3. Check for the exposed RPC function
    Query the PostgreSQL database for the presence of the 'get_identity_apikey_only' function: SELECT proname FROM pg_proc WHERE proname = 'get_identity_apikey_only'; Also check if it exists as a SECURITY DEFINER function by querying: SELECT proname, prosecurity FROM pg_proc WHERE proname = 'get_identity_apikey_only';
    Affected if The function exists and is defined as SECURITY DEFINER (proscurity = true)
  4. Verify if the RPC function requires authentication
    Check the function definition for any authentication checks. Look at the pg_proc columns or the function's SQL definition using SELECT prosrc FROM pg_proc WHERE proname = 'get_identity_apikey_only'; to see if it validates session or authentication before returning user_id.
    Affected if The function has no authentication check and directly returns user_id from API keys
  5. Test the function with a known API key
    If you have database access, test the function with a valid API key: SELECT get_identity_apikey_only('your_test_api_key'); Also test with an invalid key to confirm it behaves differently.
    Affected if The function returns a user_id for valid keys and behaves differently for invalid keys, confirming it acts as a validity oracle

A user is affected if running Capgo version lower than 12.128.2 with the 'get_identity_apikey_only' RPC function exposed as a SECURITY DEFINER without authentication, allowing enumeration of user IDs from API keys.

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. Additionally, ensure the RPC function requires proper authentication and does not expose user identity information without authorization.

Recommended fix High confidence

Capgo 12.128.2 or later

  1. Upgrade Capgo to version 12.128.2 or later to address the unauthenticated RPC function vulnerability
  2. After upgrading, verify that the get_identity_apikey_only function is no longer accessible without authentication
  3. Review API key usage logs to detect any historical exploitation attempts
  4. Monitor for any suspicious activity involving the get_orgs_v6 RPC function that could have been chained with the leaked user identifiers

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 / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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