HIGH 7.5

CVE-2026-56322: Capgo Information Disclosure in Unauthenticated /updates Endpoint

Capgo versions before 12.128.2 contain a privacy flaw that exposes private channel information to anyone on the internet. An attacker can send requests to Capgo's updates endpoint and, without logging in, probe for the names of private channels. By observing subtle differences in how the system responds to valid versus invalid channel names, attackers can enumerate private channels, discover which app versions are assigned to each channel, and extract platform-specific configuration details. This leakage happens because the system resolves channel parameters before checking whether the requester has permission to access that channel.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-200
Affected products
0 configuration(s)
Published / Modified
2026-06-23 / 2026-06-23

NVD description (verbatim)

Capgo 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.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-56322 is an information disclosure vulnerability (CWE-200) in Capgo's unauthenticated /updates endpoint. The root cause is premature parameter resolution—the endpoint accepts a defaultChannel parameter and resolves it to retrieve metadata before enforcing privacy controls. Because the resolution logic executes regardless of authentication or authorization status, attackers can fingerprint the existence and properties of private channels through timing, HTTP status code variance, or response structure differences. The vulnerability allows enumeration of private channel identifiers, discovery of assigned bundle versions, and extraction of platform-specific configuration state that should remain confidential.

Business impact

This vulnerability creates several business risks. Competitors or reconnaissance actors can map your internal application architecture by discovering private channel names and understanding your deployment strategy across platforms. Configuration data leakage may expose details about your app's feature flags, rollout patterns, or platform-specific behaviors that inform further attacks. For organizations using Capgo to manage separate staging, testing, or feature-branch deployments, the exposure of private channels directly undermines the confidentiality of development workflows and may violate compliance or data governance requirements. The unauthenticated nature means this attack is trivial to execute at scale with minimal detection risk to the attacker.

Affected systems

Capgo deployments running any version before 12.128.2 are vulnerable. The vulnerability exists in the /updates endpoint, a public-facing component, and affects any organization or individual using Capgo to manage app delivery and configuration. Verify your installed version against the patched version 12.128.2 provided by the vendor.

Exploitability

Exploitability is very high. No authentication is required, no user interaction is needed, and an attacker can execute the attack over the network using basic HTTP requests. The attacker surface is the public /updates endpoint accessible to any internet-connected client. Attackers can automate channel enumeration and configuration scraping, making large-scale reconnaissance feasible. CVSS 3.1 score of 7.5 (HIGH) reflects high impact to confidentiality with low attack complexity.

Remediation

Upgrade to Capgo version 12.128.2 or later, which enforces privacy restrictions before resolving the defaultChannel parameter. This fix ensures that authentication and authorization checks occur before any channel metadata is exposed. Review access logs to identify any pattern of requests to the /updates endpoint with invalid or suspicious channel names that may indicate prior reconnaissance activity. Assess whether any private channel names, version numbers, or configuration state require rotation or security review.

Patch guidance

Apply Capgo 12.128.2 or newer as soon as possible given the ease of exploitation. Coordinate the upgrade with your application deployment pipeline to ensure minimal disruption. Because this vulnerability is unauthenticated and requires only network access, it should be prioritized above vulnerabilities with higher attack friction. Verify the upgrade was successful by confirming the version string in your Capgo instance and retesting access control on the /updates endpoint. Check vendor release notes for any breaking changes or migration steps.

Detection guidance

Monitor logs for repeated requests to the /updates endpoint with varying or invalid defaultChannel parameter values, particularly from a single IP or subnet. Baseline normal channel request patterns (valid, authenticated channel accesses) and flag deviations such as scanning-like behavior with non-existent channel names. Inspect response metadata for any sign that channel resolution occurred before access control was applied (e.g., timing differences or structured responses to invalid channels). If using a WAF or API gateway, consider rate-limiting or blocking the /updates endpoint for unauthenticated sources, and alert on parameter fuzzing patterns.

Why prioritize this

CVE-2026-56322 should be prioritized for immediate patching because it combines unauthenticated access, low attack complexity, high information disclosure impact, and trivial automation potential. Unlike vulnerabilities that require user interaction or authentication, this flaw can be exploited at scale with minimal risk to the attacker and no legitimate detection signature. Any organization using Capgo for private or multi-environment deployments faces direct business and operational security risk. The fix is straightforward (a version upgrade) and the attack surface is well-defined.

Risk score, explained

CVSS 3.1 score of 7.5 (HIGH) is assigned because the vulnerability has network-based attack vector, low attack complexity, no privilege or user interaction requirement, and high impact to confidentiality (C:H). Integrity and availability are unaffected (I:N, A:N), but the ease and breadth of information disclosure justifies a HIGH severity rating. In practice, the true organizational risk may be higher if your private channel naming or configuration strategy is sensitive, or lower if your channels already contain only generic metadata.

Frequently asked questions

If I upgrade to 12.128.2, will I lose access to my existing channels?

No. The patch enforces authorization checks without modifying channel data or existing configurations. Backward compatibility is maintained; the change only restricts unauthenticated access to channel information.

How can I tell if my Capgo instance was attacked before I patch?

Review access logs for the /updates endpoint targeting non-existent or suspicious channel names, especially from external IP sources. Look for patterns of requests with varying parameters in short time windows, which suggest scanning behavior. However, absence of such logs does not guarantee no reconnaissance occurred, as attackers may have used minimal or intermittent probing.

Does this vulnerability allow an attacker to modify or delete channels?

No. This is a read-only information disclosure vulnerability. The attack surface is limited to enumeration and configuration leakage. An attacker cannot modify, delete, or deploy new versions via this vulnerability alone.

Are older versions of Capgo still vulnerable if I restrict network access to the /updates endpoint?

Network segmentation and authentication gateways provide defense-in-depth, but they do not remediate the underlying flaw. You should still upgrade to 12.128.2 to ensure the service itself enforces proper access control, rather than relying solely on network perimeter controls.

This analysis is provided for informational and defensive security purposes. It is based on the disclosed CVE details and vendor advisories current as of June 2026. No exploit code or weaponized proof-of-concept is included or intended. Security teams must verify patch version numbers, affected product versions, and compatibility with their specific environment against the vendor's official advisory and release notes. Testing should be conducted in a controlled environment before production deployment. This document does not constitute legal, compliance, or vendor-specific advice; consult your vendor and internal security policies for definitive guidance. Source: NVD (public-domain), retrieved 2026-07-29. Analysis generated by SEC.co (claude-haiku-4-5).