Cross-organization deletion via scoped key privilege inheritance
Published Jul 8, 2026 · Updated Jul 8, 2026
Improper authorization in Capgo before 12.128.2 allows remote authenticated users to delete assets and RBAC bindings across organizations. The rbac_check_permission_direct path accepts the API key owner's user privileges before enforcing the key's limited_to_orgs scope, then service-role operations delete out-of-scope images or role bindings. Exploitation requires a write-mode key scoped to one organization whose owner has administrative rights in both the permitted and targeted organizations.
Summary
What happened
Improper authorization in Capgo before 12.128.2 allows remote authenticated users to delete assets and RBAC bindings across organizations. The rbac_check_permission_direct path accepts the API key owner's user privileges before enforcing the key's limited_to_orgs scope, then service-role operations delete out-of-scope images or role bindings. Exploitation requires a write-mode key scoped to one organization whose owner has administrative rights in both the permitted and targeted organizations.
The record
- CVE
- CVE-2026-56246
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-285, T1531
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.128.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-ccm4-hf72-p28m reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo