Credential tampering via missing app-scope checks
Published Jun 23, 2026 · Updated Jun 23, 2026
Authorization bypass in Capgo before 12.128.2 allows remote authenticated users to manage sibling API keys outside an allowed app scope. The public API key get, put, delete, and post handlers accept mode=all keys but reject limited_to_orgs only, leaving limited_to_apps unenforced. Possession of an app-limited all key is required; it can enumerate, modify, or delete same-account sibling keys and disrupt dependent workflows.
Summary
What happened
Authorization bypass in Capgo before 12.128.2 allows remote authenticated users to manage sibling API keys outside an allowed app scope. The public API key get, put, delete, and post handlers accept mode=all keys but reject limited_to_orgs only, leaving limited_to_apps unenforced. Possession of an app-limited all key is required; it can enumerate, modify, or delete same-account sibling keys and disrupt dependent workflows.
The record
- CVE
- CVE-2026-56225
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-269, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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-hwc7-j2p6-43xp proof of conceptproof 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