dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-56295

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 an authorization bypass vulnerability in webhook management endpoints that allows non-expiring API keys to bypass the require_apikey_expiration organization policy. The checkWebhookPermission function fails to call apikeyHasOrgRightWithPolicy, enabling attackers with legacy non-expiring keys to list, create, and delete webhooks despite explicit organizational policy requiring key expiration.

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

The checkWebhookPermission function in Capgo before 12.128.2 fails to call apikeyHasOrgRightWithPolicy, allowing non-expiring API keys to bypass the require_apikey_expiration organization policy. This enables attackers with legacy non-expiring keys to list, create, and delete webhooks despite explicit organizational policy requiring key expiration.

MitigationUpgrade to Capgo 12.128.2 or later to obtain the patch, and rotate any compromised non-expiring API keys to prevent continued abuse.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 instance for its current version number (typically via admin panel, API endpoint, or package metadata file in the installation directory)
    Affected if version is lower than 12.128.2 (e.g., 12.128.1, 12.127.x, or any version before 12.128.2)
  2. List existing API keys
    Access the organization API key management interface or query the internal keys table to retrieve all registered API keys and their expiration settings
    Affected if any API key has no expiration date set (null, empty, or a far-future date indicating legacy non-expiring behavior)
  3. Verify require_apikey_expiration policy status
    Check the organization security or policy configuration for the require_apikey_expiration setting (typically found in organization settings, security policies, or via API)
    Affected if the policy is explicitly enabled or set to require key expiration
  4. Examine webhook permission enforcement
    Attempt to create, list, or delete a webhook using a non-expiring API key while the require_apikey_expiration policy is active, or review API access logs for webhook operations performed by keys without expiration
    Affected if non-expiring keys successfully perform webhook operations despite the expiration policy being enforced

You are affected if your Capgo version is below 12.128.2 AND you have non-expiring API keys in use while the require_apikey_expiration policy is enabled, as these keys can bypass webhook permission controls.

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 12.128.2 or later to obtain the patch, and rotate any compromised non-expiring API keys to prevent continued abuse.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. Upgrade Capgo to version 12.128.2 or later to resolve the authorization bypass in webhook management endpoints
  2. After upgrading, verify that the checkWebhookPermission function now properly calls apikeyHasOrgRightWithPolicy
  3. Confirm that the require_apikey_expiration organization policy is now enforced for all API keys, including previously non-expiring legacy keys
  4. Test that webhook listing, creation, and deletion operations are properly restricted according to the organization's API key expiration policy

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
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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