dbcve.org
CWE-203Weakness · CWE-203

CVE-2026-56327

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 an information disclosure vulnerability in the public.invite_user_to_org RPC function that allows unauthenticated attackers to enumerate organization existence by observing distinct error responses. Attackers can call the SECURITY DEFINER function with a publishable API key to determine if an organization ID exists based on NO_ORG versus NO_RIGHTS responses, enabling tenant enumeration attacks.

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 in the public.invite_user_to_org RPC function. Attackers with a publishable API key can call this SECURITY DEFINER function and distinguish between NO_ORG (organization doesn't exist) and NO_RIGHTS (organization exists but no permission) error responses, enabling tenant/organization enumeration.

MitigationUpdate Capgo to version 12.128.2 or later. Alternatively, normalize error responses to prevent enumeration and ensure proper authorization checks are performed before revealing organization existence.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
    Retrieve the installed Capgo version via package.json, API endpoint, or deployment metadata. Compare it to the fixed version 12.128.2.
    Affected if Installed version is earlier than 12.128.2
  2. Verify publishable API keys are in use
    Review API key configuration to confirm publishable (public) keys are enabled or distributed to untrusted users.
    Affected if Publishable API keys are actively used in the environment
  3. Test public.invite_user_to_org error responses
    Call the public.invite_user_to_org RPC function using a publishable API key with a non-existent organization identifier, then with a valid but unauthorized organization identifier. Compare the error messages returned.
    Affected if Different error messages are returned for non-existent organizations versus existing organizations without permissions (e.g., NO_ORG vs NO_RIGHTS distinctions are visible)
  4. Check function security definition
    Inspect the public.invite_user_to_org function definition in the database or codebase. Verify if it uses SECURITY DEFINER and what authorization checks are performed.
    Affected if Function is defined as SECURITY DEFINER without proper pre-authorization validation

A user is affected if their Capgo installation is version earlier than 12.128.2 AND they expose publishable API keys to untrusted parties, allowing them to distinguish NO_ORG from NO_RIGHTS errors and enumerate organizations.

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

Update Capgo to version 12.128.2 or later. Alternatively, normalize error responses to prevent enumeration and ensure proper authorization checks are performed before revealing organization existence.

Recommended fix High confidence

12.128.2 or later

  1. 1. Identify the current Capgo installation version by checking the application or deployment configuration
  2. 2. Review the Capgo upgrade documentation for your specific deployment method (e.g., npm package, Docker container, self-hosted)
  3. 3. Back up all critical data, configurations, and database state before proceeding with the upgrade
  4. 4. Upgrade Capgo to version 12.128.2 or later by updating dependencies or redeploying the container image
  5. 5. Verify the upgrade was successful by checking the running version matches 12.128.2 or higher
  6. 6. Test the public.invite_user_to_org RPC function to confirm the vulnerability is remediated (error responses should now be uniform)
Caveat Review Capgo release notes between your current version and 12.128.2 for any breaking changes that may affect your integration

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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