dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-56230

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 a broken object level authorization vulnerability in middlewareKey() that accepts the client-controlled x-limited-key-id header without validating ownership, allowing authenticated users to adopt cross-tenant limited keys. Attackers can supply another tenant's limited key ID to bypass authorization checks and access unauthorized cross-tenant resources across multiple API 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 broken object level authorization (BOLA) vulnerability in the middlewareKey() function. The middleware accepts the x-limited-key-id header from client requests without validating that the authenticated user owns or has access to the specified key, allowing cross-tenant resource access by supplying another tenant's limited key ID.

MitigationUpgrade to Capgo version 12.128.2 or later which includes proper ownership validation for the x-limited-key-id header. As an immediate workaround, implement request-level authorization checks to verify the authenticated user's tenant matches the key's owner before processing requests.

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. Identify Capgo installation version
    Run 'capgo --version' or check package.json for @capgo/api version, or query the Capgo API endpoint /info for the version field
    Affected if Version is below 12.128.2 (e.g., 12.128.1, 12.120.0, etc.)
  2. Locate middlewareKey function usage
    Search source code for 'middlewareKey' function calls, typically in API route handlers or middleware configuration files
    Affected if The middlewareKey function is imported and used in the application routing or middleware stack
  3. Verify x-limited-key-id header processing
    Inspect the middlewareKey function implementation or configuration to confirm it reads the 'x-limited-key-id' request header
    Affected if The code explicitly processes the x-limited-key-id header without owner validation logic
  4. Check authorization validation logic
    Review the middlewareKey function for tenant ownership validation - look for code that verifies the authenticated user's tenant matches the key's owner before allowing access
    Affected if No tenant or ownership check exists before using the key from the x-limited-key-id header
  5. Audit API endpoints using limited keys
    Review API routes that accept x-limited-key-id and determine if they handle cross-tenant data
    Affected if Endpoints accept the header and return data from keys belonging to different tenants

You are affected if running Capgo version below 12.128.2 AND your application uses the x-limited-key-id header in the middlewareKey function without validating that the authenticated user owns the specified key.

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 which includes proper ownership validation for the x-limited-key-id header. As an immediate workaround, implement request-level authorization checks to verify the authenticated user's tenant matches the key's owner before processing requests.

Recommended fix High confidence

Upgrade to Capgo version 12.128.2 or later

  1. 1. Identify the current Capgo installation version by checking the package.json, package-lock.json, or running 'capgo --version' or checking the deployed application version
  2. 2. If the version is below 12.128.2, prepare for upgrade by reviewing the Capgo upgrade documentation for your deployment method
  3. 3. Upgrade Capgo to version 12.128.2 or later using your package manager (e.g., npm install @capgo/capacitor-updater@latest or the specific version command)
  4. 4. Verify the upgrade was successful by checking the installed version
  5. 5. Test the application to confirm the x-limited-key-id header validation is working correctly and cross-tenant access is prevented
Caveat Review Capgo release notes between your current version and 12.128.2 for any breaking changes or deprecated API usage

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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