CVE-2026-56246
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 · uneditedCapgo before 12.128.2 contains a broken access control vulnerability in the organization management API where a scoped API key (limited_to_orgs) inherits its owner-user's permissions, allowing destructive cross-organization actions. When a user is an admin in two organizations and creates a write-mode API key restricted to one organization, that key can still perform destructive operations (e.g., DELETE /organization, DELETE /organization/members) against another organization. The root cause is route-level authorization (rbac_check_permission_direct) that evaluates the key owner's user privileges before enforcing the API key's limited_to_orgs scope.
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 confidenceThe vulnerability exists in the route-level authorization function `rbac_check_permission_direct` which evaluates the API key owner's user-level admin privileges before enforcing the `limited_to_orgs` scope restriction. When a user with admin permissions in two organizations creates a write-mode API key scoped to only one organization, the authorization check incorrectly uses the owner's broader admin privileges rather than respecting the key's organization restrictions, allowing destructive operations (DELETE /organization, DELETE /organization/members) against organizations outside the key's defined scope.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo installation and versionCheck the installed Capgo version by reviewing package.json, running 'capgo --version', or querying the application directlyAffected if The installed version is earlier than 12.128.2 and the application uses the API key authorization system
-
Identify users with admin permissions across multiple organizationsQuery the user management system or database to list users who have admin role in more than one organizationAffected if There exists a user account with admin-level permissions in two or more organizations
-
Check for API keys with limited_to_orgs scope restrictionsInspect the API key configuration to identify keys that have the 'limited_to_orgs' scope parameter defined, which restricts the key to specific organizationsAffected if API keys exist with the limited_to_orgs scope parameter set to restrict access to a subset of organizations
-
Identify write-mode API keys scoped to a single organizationReview API key definitions to find keys that are configured with write permissions (create/update/delete) but have limited_to_orgs set to only one organization when the key owner has admin rights in multiple orgsAffected if A write-mode API key is scoped to only one organization while its owner has admin privileges in other organizations outside that scope
-
Verify authorization behavior for cross-organization DELETE operationsTest or inspect logs for DELETE /organization and DELETE /organization/members requests made using an API key with limited_to_orgs scope, to see if operations against organizations outside the key scope succeedAffected if DELETE operations against organizations not listed in the limited_to_orgs scope are permitted when using an API key owned by a multi-org admin
You are affected if running a Capgo version before 12.128.2 with a user who has admin permissions in multiple organizations and uses a write-mode API key scoped to only one organization via limited_to_orgs, allowing unauthorized cross-organization destructive operations.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Capgo version 12.128.2 or later, which implements proper scope enforcement in the authorization logic to respect the `limited_to_orgs` restriction before evaluating user-level permissions.
Capgo 12.128.2 or later
- Identify the currently installed Capgo version by checking your package.json or running your package manager's version command
- Upgrade Capgo to version 12.128.2 or later using your package manager (e.g., npm install capgo@latest or npm install capgo@^12.128.2)
- After upgrading, test that API keys with limited_to_orgs scope now correctly respect their organization restrictions
- Verify that scoped API keys can no longer perform destructive operations (DELETE /organization, DELETE /organization/members) on organizations outside their defined scope
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56246 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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