dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56079

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 a cross-tenant authorization bypass vulnerability in PostgREST endpoints that allows org-scoped read API keys to access other tenants' webhook secrets and delivery logs. Attackers can query the webhooks and webhook_deliveries endpoints to exfiltrate HMAC signing secrets and delivery payloads, enabling forged webhook events against victim organizations.

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 · moderate confidence

Capgo before 12.128.2 has a cross-tenant authorization bypass in PostgREST endpoints where org-scoped read API keys can access other tenants' webhook data. Attackers can query webhooks and webhook_deliveries endpoints to exfiltrate HMAC signing secrets and delivery payloads, then forge webhook events against victim organizations.

MitigationUpgrade Capgo to version 12.128.2 or later to patch the authorization bypass. Review and rotate any exposed HMAC signing secrets and audit API key usage for unauthorized cross-tenant access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 (self-hosted instance, Docker container, or managed service) and retrieve the installed version number. Common methods: check package.json, Docker image tag, admin dashboard 'About' page, or API endpoint like /api/version
    Affected if Version is below 12.128.2 (e.g., 12.128.1, 12.127.x, or earlier)
  2. Confirm PostgREST API is enabled
    Verify that PostgREST endpoints are accessible in the Capgo environment. Check if the API server exposes REST endpoints at paths such as /rest/v1/webhooks or similar. Inspect server configuration files or network routes for PostgREST service availability
    Affected if PostgREST endpoints are reachable and serve webhook-related tables (webhooks, webhook_deliveries)
  3. Review API key scopes and tenant isolation
    Examine existing API keys in the Capgo system, particularly those with 'read' scope and 'org' level access. Check if keys are tied to a specific organization ID and whether the API enforces tenant boundaries when querying webhooks table
    Affected if Org-scoped read API keys exist and can query webhooks or webhook_deliveries tables without explicit tenant filtering
  4. Test cross-tenant webhook access
    Using an org-scoped read API key from one organization, attempt to query the webhooks or webhook_deliveries endpoints with a different organization's ID in the request. Compare returned data against the expected scoped organization
    Affected if API key returns webhook data (including HMAC signing secrets or delivery payloads) belonging to a different tenant than the key's owner
  5. Inspect webhook data for sensitive exposure
    Review the actual contents returned by webhooks and webhook_deliveries endpoints. Check if HMAC signing secrets, delivery payloads, or other sensitive configuration data is exposed in API responses that should be restricted to the key's organization
    Affected if API responses include HMAC secrets or delivery payloads from organizations other than the one associated with the API key

You are affected if Capgo version is below 12.128.2 AND org-scoped read API keys can access webhook data from other tenants via PostgREST endpoints.

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 authorization bypass. Review and rotate any exposed HMAC signing secrets and audit API key usage for unauthorized cross-tenant access.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the current Capgo installation version by checking the running instance or deployment configuration
  2. 2. If the current version is before 12.128.2, plan for an upgrade to version 12.128.2 or later
  3. 3. Review Capgo upgrade documentation for your deployment method (e.g., npm package, Docker container, self-hosted)
  4. 4. Perform the upgrade following standard upgrade procedures for your installation method
  5. 5. After upgrade, verify that org-scoped API keys can no longer access cross-tenant webhook secrets and delivery logs
  6. 6. Consider rotating any HMAC signing secrets that may have been exposed during the vulnerability window

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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