dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-56232

HIGH · 8.8 CVSS v3.1 Published 2026-06-24
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 fails to enforce limited_to_orgs and limited_to_apps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the unrestricted parent key instead of the scoped subkey.

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 an authorization bypass in the middlewareKey function. When subkeys are specified via the x-limited-key-id header, the system fails to enforce the limited_to_orgs and limited_to_apps constraints. Attackers can reference their own subkeys to bypass scope restrictions, causing downstream handlers to use the unrestricted parent key instead of the properly scoped subkey.

MitigationUpgrade to Capgo version 12.128.2 or later which enforces subkey scope constraints. As an interim measure, validate that subkey restrictions are properly applied before processing any downstream 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. Check Capgo version
    Retrieve the installed Capgo version from your package.json, package-lock.json, or by running 'npm list capgo' or the Capgo CLI version command
    Affected if The installed version is earlier than 12.128.2
  2. Verify subkey usage with x-limited-key-id header
    Review your application code and API configurations to determine if requests use the x-limited-key-id header to specify subkeys
    Affected if The x-limited-key-id header is used to reference subkeys in API requests
  3. Inspect subkey constraint configurations
    Examine subkey configurations for limited_to_orgs and limited_to_app restrictions in your Capgo key management settings
    Affected if Subkeys are configured with limited_to_orgs or limited_to_app constraints
  4. Check middlewareKey function configuration
    Review the Capgo middlewareKey function implementation to verify if it properly enforces subkey scope constraints before passing requests to downstream handlers
    Affected if The middleware does not validate that subkey restrictions are applied before processing requests

You are affected if you are running Capgo before version 12.128.2 and using subkeys with the x-limited-key-id header that have limited_to_orgs or limited_to_app restrictions

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 enforces subkey scope constraints. As an interim measure, validate that subkey restrictions are properly applied before processing any downstream requests.

Recommended fix High confidence

Capgo version 12.128.2 or later

  1. 1. Identify the current version of Capgo in use by checking package.json, lock files, or the running application
  2. 2. Upgrade Capgo to version 12.128.2 or later to resolve the authorization bypass in the middlewareKey function
  3. 3. After upgrading, verify that subkey scope restrictions (limited_to_orgs and limited_to_apps) are now properly enforced
  4. 4. Test that subkeys with restricted scopes cannot bypass their defined limitations via the x-limited-key-id header
  5. 5. Confirm that downstream route handlers now correctly use the scoped subkey rather than the unrestricted parent key

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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