dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-56241

HIGH · 8.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click 5 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 privilege escalation vulnerability where demoted super_admin users retain access to delete_non_compliant_bundles and count_non_compliant_bundles RPCs due to stale org_users.user_right column not being cleared during role binding deletion. Attackers can exploit this by maintaining a previously granted super_admin role to enumerate and bulk delete non-compliant bundles across the entire organization indefinitely.

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 fails to clear the org_users.user_right column when role bindings are deleted, causing demoted super_admin users to retain access to delete_non_compliant_bundles and count_non_compliant_bundles RPCs. This allows former admins to enumerate and bulk delete non-compliant bundles organization-wide indefinitely.

MitigationUpgrade to Capgo 12.128.2 or later, and manually audit and clear stale user_right values in the org_users table for any demoted super_admin users.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 Capgo version
    Query the Capgo application or database for the current version number. Compare against the affected range (before 12.128.2).
    Affected if Running Capgo version 12.128.1 or earlier
  2. Inspect org_users.user_right column
    Query the org_users table for records that have a non-null or non-empty value in the user_right column. Use: SELECT user_id, email, user_right FROM org_users WHERE user_right IS NOT NULL AND user_right != '';
    Affected if Any user has a non-empty user_right value after being demoted from super_admin role
  3. Identify potentially demoted super_admin users
    Cross-reference users with elevated user_right values against current role assignments to determine if they still hold super_admin status or were demoted.
    Affected if A user has elevated user_right but no longer has current super_admin role binding
  4. Verify RPC access for demoted users
    Check if users with stale user_right can still call delete_non_compliant_bundles or count_non_compliant_bundles RPC methods despite not being current super_admins.
    Affected if Former super_admin users without current role bindings can still execute these RPCs

You are affected if running Capgo before 12.128.2 AND any demoted super_admin user retains non-null user_right values in the org_users table.

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 12.128.2 or later, and manually audit and clear stale user_right values in the org_users table for any demoted super_admin users.

Recommended fix Moderate confidence

Capgo version 12.128.2 or later

  1. 1. Identify the current Capgo application version in use by checking the application's version settings or deployment configuration.
  2. 2. If the current version is before 12.128.2, plan for an upgrade to version 12.128.2 or later.
  3. 3. Before applying the upgrade in production, test the new version in a staging or development environment to verify the privilege escalation vulnerability is remediated.
  4. 4. Confirm that demoted super_admin users no longer have access to delete_non_compliant_bundles and count_non_compliant_bundles RPCs after the upgrade.
  5. 5. Apply the upgrade to production environment following standard deployment procedures.
  6. 6. Verify that the org_users.user_right column is properly cleared for demoted users after role binding deletion.

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-56241 — 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-56241 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