Unauthenticated tenant metadata disclosure via channel_self
Published Jun 22, 2026 · Updated Jun 22, 2026
Information disclosure in Capgo before 12.128.2 allows remote attackers to enumerate private channels and tenant state via channel_self. The unauthenticated GET handler omits checkPermission(), accepts app_id without device_id or signature validation, and returns listCompatibleChannels() metadata plus distinct app and plan errors. No account, API key, or device binding is required; exposed data is limited to channel metadata, valid application identifiers, and subscription status.
Summary
What happened
Information disclosure in Capgo before 12.128.2 allows remote attackers to enumerate private channels and tenant state via channel_self. The unauthenticated GET handler omits checkPermission(), accepts app_id without device_id or signature validation, and returns listCompatibleChannels() metadata plus distinct app and plan errors. No account, API key, or device binding is required; exposed data is limited to channel metadata, valid application identifiers, and subscription status.
The record
- CVE
- CVE-2026-56323
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-200, T1595.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 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
- Unauthenticated channel_self HTTP 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