dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-56216

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
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 scope escalation vulnerability in the POST /functions/v1/apikey endpoint that allows app-limited API keys to mint unrestricted keys by setting empty limits. Attackers with a compromised app-limited key can create an unrestricted key with org-wide access to resources like app listings and other protected endpoints.

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 a scope escalation vulnerability in the POST /functions/v1/apikey endpoint. Attackers with a compromised app-limited API key can mint unrestricted keys with organization-wide access by setting empty limits in the request, bypassing the intended app-scoped restrictions.

MitigationUpgrade to Capgo version 12.128.2 or later. Additionally, audit for any unauthorized unrestricted API keys that may have been created using this vulnerability.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine your Capgo version
    Check your Capgo installation or package.json for the installed version number. If using the Capgo cloud service, contact support or check your dashboard for the version information.
    Affected if The installed version is before 12.128.2
  2. Identify API keys with organization-wide access
    Review your Capgo API key inventory and identify any keys that have organization-level or unrestricted scope. Look for keys where the scope field shows full organization access rather than limited app-specific permissions.
    Affected if There are API keys with organization-wide scope that were created from app-limited keys or that bypass normal app-scoped restrictions
  3. Check API key creation audit logs
    Examine Capgo audit logs or access logs for POST requests to /functions/v1/apikey endpoint. Look for patterns where app-scoped keys were used to create new keys with elevated permissions or empty limits.
    Affected if There are log entries showing app-limited keys creating unrestricted keys, or requests to /functions/v1/apikey with empty or missing limits parameters
  4. Verify API key request behavior
    If you have a test environment, attempt to create a new API key using an app-scoped key with empty limits in the request body. Observe whether the system accepts this and grants organization-wide access.
    Affected if The system allows an app-scoped API key to successfully create an unrestricted organization-wide key by setting empty limits

You are affected if your Capgo version is before 12.128.2 and you have API keys with organization-wide scope that could have been created through the vulnerable endpoint using app-scoped credentials.

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 version 12.128.2 or later. Additionally, audit for any unauthorized unrestricted API keys that may have been created using this vulnerability.

Recommended fix Moderate confidence

12.128.2 or later

  1. Upgrade Capgo to version 12.128.2 or later to remediate the scope escalation vulnerability
  2. After upgrading, verify that app-limited API keys can no longer create unrestricted keys with org-wide access
  3. Review existing API keys in your organization to ensure no unauthorized unrestricted keys were created during the vulnerable period

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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