CVE-2026-56328
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCapgo before 12.128.2 allows multiple public channels for the same app and platform to coexist simultaneously, while unnamed /updates requests without defaultChannel implicitly resolve to a single hidden winner channel. An authorized app or channel manager can create ambiguous default update state and silently influence which bundle unnamed clients receive, breaking release routing integrity and predictability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCapgo before version 12.128.2 has a logic flaw where multiple public channels can coexist for the same app and platform, but unnamed /updates requests without an explicit defaultChannel resolve to a single hidden winner channel. An authorized app or channel manager can exploit this ambiguity to silently influence which update bundle unnamed clients receive, breaking the expected release routing integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Capgo SDK versionLocate the Capgo SDK package in your project (typically in package.json for React Native, or Gradle/Podfile for native) and run 'npm list @capgo/capacitor-updater' or check the installed package version directlyAffected if Version is below 12.128.2 (e.g., 12.128.1, 12.128.0, any 12.x.x below 12.128.2, or any earlier major version)
-
Review channel configurations in Capgo dashboardLog into Capgo dashboard, navigate to the channels section for each app, and list all public channels for each platform (iOS/Android)Affected if More than one public channel exists for the same app and platform combination without explicit defaultChannel assignment
-
Audit update request implementationSearch your codebase for Capgo update API calls (such as 'checkUpdate' or '/updates' endpoint calls) and inspect whether 'defaultChannel' or 'channel' parameter is explicitly passed in all requestsAffected if Any update requests are made without explicitly specifying the defaultChannel parameter, relying on implicit resolution
-
Check for hidden winner channelIn Capgo dashboard, examine channel visibility settings and look for any channel marked as hidden or default that could win the implicit resolution when multiple public channels existAffected if A hidden or implicit default channel exists that would win the resolution when multiple public channels are present for the same app/platform
Your environment is affected if you use a Capgo SDK version below 12.128.2 AND have multiple public channels for the same app/platform while your app sends update requests without explicitly specifying the defaultChannel parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Capgo to version 12.128.2 or later, audit all existing channel configurations to ensure no ambiguous default state exists, and explicitly specify defaultChannel in all update requests to prevent implicit resolution.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data