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

CVE-2026-56222

HIGH · 7.2 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 POST /private/role_bindings that fails to verify app_id ownership during app-scoped role binding creation. An attacker with administrative privileges in one organization can create role bindings targeting applications owned by other organizations, enabling unauthorized read and modification of victim applications.

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 POST /private/role_bindings endpoint that does not verify app_id ownership when creating app-scoped role bindings. An attacker with admin privileges in one organization can create role bindings for applications owned by other organizations, allowing unauthorized read and modification of victim applications.

MitigationUpgrade Capgo to version 12.128.2 or later which includes proper app_id ownership verification in the role_bindings endpoint.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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
    Access the Capgo admin dashboard or use the CLI/API to query the installed version (often available via /api/version endpoint, admin settings page, or package.json if self-hosted)
    Affected if The installed version is below 12.128.2 (e.g., 12.128.1, 12.127.x, or earlier)
  2. Verify role_bindings endpoint accessibility
    Send a POST request to /private/role_bindings with valid admin credentials and inspect whether the request succeeds without additional app_id ownership validation
    Affected if The endpoint accepts requests without verifying that the authenticated organization owns the referenced app_id
  3. Inspect existing role bindings for cross-organization app references
    Query the role_bindings API or database table to list all role bindings; check the app_id field in each binding and compare the organization ID associated with each binding to the organization that owns the referenced app
    Affected if Any role binding exists where the app_id belongs to a different organization than the binding's owner organization
  4. Review audit logs for suspicious role binding creation
    Examine Capgo audit logs or access logs for POST requests to /private/role_bindings that create bindings with app_ids from organizations other than the requester's organization
    Affected if Logs show role bindings created for apps owned by other organizations by a user who should not have access to those apps

You are affected if your Capgo version is below 12.128.2 AND your organization has users with admin privileges who could potentially create unauthorized cross-organization role bindings.

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 Capgo to version 12.128.2 or later which includes proper app_id ownership verification in the role_bindings endpoint.

Recommended fix High confidence

Capgo version 12.128.2 or later

  1. 1. Identify the current Capgo installation version by checking the application or deployment configuration
  2. 2. Review the application's dependency management system (package.json, Gemfile, requirements.txt, etc.) to locate the Capgo package version
  3. 3. Update the Capgo package dependency to version 12.128.2 or later in your dependency manifest
  4. 4. Run the dependency update command appropriate to your package manager (e.g., npm update, pip install -U, bundle update)
  5. 5. Verify the new version is installed: check the lock file or run a version query command
  6. 6. Test the application functionality, specifically: verify that POST /private/role_bindings now correctly validates app_id ownership
  7. 7. Deploy the updated application to your staging environment and conduct security testing to confirm the authorization bypass is fixed
  8. 8. Deploy to production after successful validation
Caveat Review Capgo release notes between your current version and 12.128.2 for any API changes or deprecations that may affect your integration

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
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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