CVE-2026-56322
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 contains an information disclosure vulnerability in the unauthenticated /updates endpoint that resolves the defaultChannel parameter before enforcing privacy restrictions, allowing attackers to enumerate private channels and leak version/config state. Unauthenticated attackers can probe private channel names and distinguish valid channels from nonexistent ones based on response differences, revealing assigned bundle versions and platform-specific configuration details.
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 · high confidenceCapgo before 12.128.2 has an information disclosure vulnerability where the /updates endpoint resolves the defaultChannel parameter before enforcing privacy restrictions, allowing unauthenticated attackers to enumerate private channel names by observing response differences and leak version/configuration state.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installation and versionLocate the Capgo installation in your environment and retrieve the installed version number. This may be found in package.json, a config file, or by running 'capgo --version' or checking your dependency lock file.Affected if The installed version is earlier than 12.128.2 (e.g., 12.128.1, 12.128.0, or any version below 12.128.2).
-
Verify /updates endpoint exposureConfirm that the /updates endpoint is accessible from your Capgo deployment. Check your web server or API gateway configuration to determine if this endpoint is exposed to the network or internet.Affected if The /updates endpoint is publicly accessible without authentication.
-
Check for defaultChannel configurationInspect your Capgo configuration files (such as app.config, capgo.config, or equivalent) for any usage of the 'defaultChannel' parameter or setting that specifies a default update channel.Affected if A defaultChannel is configured and points to a private or internal channel name.
-
Test endpoint behavior with different channel valuesMake unauthenticated HTTP requests to the /updates endpoint using different defaultChannel parameter values (e.g., a known public channel versus a suspected private channel) and compare the response differences in status codes, error messages, or response content.Affected if Different defaultChannel values produce distinguishable responses that leak information about the existence or configuration of private channels.
-
Review authentication enforcement orderExamine how your Capgo server processes requests to /updates. Determine if the defaultChannel parameter is resolved (processed) before or simultaneously with the authentication/authorization check. Check server logs or code for the request handling order.Affected if The defaultChannel parameter is resolved and processed before privacy restrictions or authentication are enforced on the request.
You are affected if your Capgo version is below 12.128.2 and the /updates endpoint is accessible without proper authentication enforcement occurring before defaultChannel parameter resolution.
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.
dbcve · scopedUpgrade to Capgo 12.128.2 or later. Until then, implement additional authentication/authorization checks on the /updates endpoint before parameter resolution, and add rate limiting to mitigate channel enumeration attempts.
Capgo version 12.128.2 or later
- Identify the current installed version of Capgo in your deployment
- Review the Capgo release notes or changelog for version 12.128.2 to confirm the security fix addresses CVE-2026-56322
- Upgrade Capgo to version 12.128.2 or later following the official upgrade documentation
- After upgrading, verify that the /updates endpoint now properly enforces privacy restrictions before resolving the defaultChannel parameter
- Test that unauthenticated requests to /updates can no longer enumerate private channels or distinguish valid from invalid channel names
- Confirm that private channel information (bundle versions, platform-specific config) is no longer exposed in unauthenticated responses
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56322 — 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-56322 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