Release-routing manipulation via ambiguous public channels
Published Jun 30, 2026 · Updated Jun 30, 2026
Improper release routing in Capgo before 12.128.2 allows remote authenticated users to influence bundles delivered by update checks. The channel-selection logic permits multiple public channels for one app and platform, then resolves an unnamed /updates request without defaultChannel to one implicit winner. App or channel management access is required, and the resulting ambiguity compromises update-routing integrity without a reported confidentiality or availability impact.
Summary
What happened
Improper release routing in Capgo before 12.128.2 allows remote authenticated users to influence bundles delivered by update checks. The channel-selection logic permits multiple public channels for one app and platform, then resolves an unnamed /updates request without defaultChannel to one implicit winner. App or channel management access is required, and the resulting ambiguity compromises update-routing integrity without a reported confidentiality or availability impact.
The record
- CVE
- CVE-2026-56328
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-670, T1195.002
- 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
No public exploit references are available in this record.
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