Cross-tenant resource access via unchecked key ownership
Published Jun 30, 2026 · Updated Jun 30, 2026
Broken object level authorization in Capgo before 12.128.2 allows remote authenticated users to access cross-tenant resources via a crafted header. The middlewareKey() function resolves the client-controlled x-limited-key-id value and replaces the request authentication context without checking whether the referenced limited key belongs to the authenticated API-key owner. Any valid API key is sufficient; the adopted scope exposes another tenant's applications and permits unauthorized operations on routes that share the middleware.
Summary
What happened
Broken object level authorization in Capgo before 12.128.2 allows remote authenticated users to access cross-tenant resources via a crafted header. The middlewareKey() function resolves the client-controlled x-limited-key-id value and replaces the request authentication context without checking whether the referenced limited key belongs to the authenticated API-key owner. Any valid API key is sufficient; the adopted scope exposes another tenant's applications and permits unauthorized operations on routes that share the middleware.
The record
- CVE
- CVE-2026-56230
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-639, CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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.
Weakness, pattern, technique
Public exploit references
- Two-account x-limited-key-id cross-tenant 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