dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56303

HIGH · 7.5 CVSS v3.1 Published 2026-07-11
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 6 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 find_apikey_by_value PostgreSQL function marked SECURITY DEFINER and executable by the anon role. Unauthenticated attackers can call this function via the /rest/v1/rpc/find_apikey_by_value endpoint to retrieve sensitive API key metadata including user_id, mode, org scoping, and expiration details when supplied a valid key value.

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 has an information disclosure vulnerability where the PostgreSQL function find_apikey_by_value, marked as SECURITY DEFINER and executable by the anon role, can be called by unauthenticated attackers via the /rest/v1/rpc/find_apikey_by_value endpoint to retrieve sensitive API key metadata including user_id, mode, organization scoping, and expiration details when supplied a valid key value.

MitigationUpgrade to Capgo version 12.128.2 or later. Additionally, review and restrict the anon role's permissions on the find_apikey_by_value function to prevent unauthenticated access until the upgrade is applied.

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. Check Capgo version
    Locate the installed Capgo version in your deployment configuration, package.json, or running application metadata. Compare this version number to the affected range (before 12.128.2).
    Affected if The installed version is lower than 12.128.2 (e.g., 12.128.1, 12.127.x, or any earlier version).
  2. Verify the RPC endpoint is exposed
    Attempt to access or probe the /rest/v1/rpc/find_apikey_by_value endpoint on your Capgo server (e.g., via curl or HTTP request tool). This endpoint is part of the PostgREST interface.
    Affected if The endpoint responds to unauthenticated HTTP requests (returns any response rather than 401/403).
  3. Check if the anon role has execute permission on find_apikey_by_value
    Query your PostgreSQL database: SELECT proname, prosrc FROM pg_proc WHERE proname = 'find_apikey_by_value'; Then check role permissions: SELECT relname, relacl FROM pg_class WHERE relname = 'find_apikey_by_value'; Look for the 'anon' role in the ACL.
    Affected if The 'anon' role appears in the function permissions with EXECUTE capability, allowing unauthenticated users to invoke it.
  4. Confirm API keys exist in the system
    Check if any API keys have been created in the Capgo system by querying the apikeys table (if accessible with admin credentials): SELECT id, user_id, mode, organization_id FROM apikeys;
    Affected if There are active API keys stored in the database - this is a prerequisite for the vulnerability to be exploitable (attacker needs a valid key value to query).

You are affected if your Capgo version is before 12.128.2 AND the /rest/v1/rpc/find_apikey_by_value endpoint is accessible to unauthenticated users AND the anon role can execute the find_apikey_by_value function AND there are valid API keys in your system that could be used as input to leak metadata.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Capgo version 12.128.2 or later. Additionally, review and restrict the anon role's permissions on the find_apikey_by_value function to prevent unauthenticated access until the upgrade is applied.

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-56303 — 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-56303 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