dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-56323

HIGH · 7.5 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Capgo before 12.128.2 contains an information disclosure vulnerability in the /functions/v1/channel_self endpoint that allows unauthenticated attackers to enumerate non-public channel names and determine app existence and subscription status. Remote attackers can send GET requests with arbitrary app_id parameters to disclose internal rollout channels, enumerate valid applications across tenants, and leak billing status without authentication or device binding.

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 confidence

Capgo before 12.128.2 has an unauthenticated information disclosure vulnerability in the /functions/v1/channel_self endpoint. Attackers can send GET requests with arbitrary app_id parameters to enumerate internal rollout channels, discover valid application IDs across tenants, and leak subscription/billing status without any authentication or device binding.

MitigationUpgrade to Capgo 12.128.2 or later, and implement proper authentication and authorization checks on the channel_self endpoint to ensure users can only access channels for apps they own or have permission to view.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Capgo installation and version
    Locate the Capgo deployment in your environment and determine the installed version number. Check deployment manifests, container image tags, or configuration files where the Capgo version is recorded.
    Affected if The installed version is earlier than 12.128.2 (e.g., 12.120.0, 12.100.0, any version below 12.128.2).
  2. Confirm the /functions/v1/channel_self endpoint is exposed
    Identify the base URL for your Capgo deployment and verify that the /functions/v1/channel_self endpoint is accessible on the network. Check API gateway or routing configuration.
    Affected if The endpoint is reachable and responds to HTTP requests.
  3. Test unauthenticated access to the endpoint
    Send a GET request to https://<your-capgo-host>/functions/v1/channel_self without providing any authentication tokens, headers, or credentials. Observe the HTTP response code and body.
    Affected if The endpoint returns a successful response (2xx) without requiring authentication.
  4. Test app_id parameter enumeration
    Send GET requests to /functions/v1/channel_self with different app_id values (e.g., ?app_id=test123, ?app_id=app-uuid-1) without authentication. Compare responses to see if different app_ids return different channel, subscription, or billing information.
    Affected if Varying the app_id parameter reveals different application channels, IDs, or billing status information without authentication.

You are affected if your Capgo version is below 12.128.2 AND the /functions/v1/channel_self endpoint accepts unauthenticated GET requests with arbitrary app_id parameters to leak channel or billing data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Capgo 12.128.2 or later, and implement proper authentication and authorization checks on the channel_self endpoint to ensure users can only access channels for apps they own or have permission to view.

Recommended fix Moderate confidence

Capgo 12.128.2 or later

  1. Upgrade Capgo to version 12.128.2 or later to remediate the information disclosure vulnerability in the /functions/v1/channel_self endpoint

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56323 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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