MEDIUM 6.4

CVE-2026-56329: Capgo Cross-Tenant Preview Namespace Collision Vulnerability

Capgo versions before 12.128.2 have a namespace collision vulnerability in how preview URLs are parsed. The system decodes double underscores to dots in a way that isn't unique—meaning an attacker can register an app ID with underscores that collides with another tenant's dotted app ID. This causes preview traffic to be misrouted and can deny legitimate users access to their preview environments.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L
Weaknesses (CWE)
CWE-436
Affected products
0 configuration(s)
Published / Modified
2026-07-10 / 2026-07-10

NVD description (verbatim)

Capgo before 12.128.2 contains a cross-tenant preview namespace collision vulnerability caused by non-bijective decoding of double underscores to dots in preview hostname parsing. Attackers can register app IDs with underscores that collide with other tenants' dotted app IDs, causing preview misrouting and denial of preview access for victim applications.

3 reference(s) · View on NVD →

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

Technical summary

CVE-2026-56329 stems from non-bijective decoding logic in Capgo's preview hostname parser. When preview URLs are constructed, double underscores (__) are intended to be converted to dots (.), but the decoding process is not one-to-one: both 'app__id' and 'app.id' can decode to the same internal identifier. An authenticated attacker can exploit this by registering a malicious app ID containing underscores that hashes to the same namespace as a legitimate tenant's dotted app ID. This causes the preview system to misdirect requests and deny service to the victim application's preview functionality. The vulnerability is classified under CWE-436 (Untrusted Input in Format String).

Business impact

For Capgo users, this vulnerability undermines the reliability of preview environments—a critical part of the development workflow. Attackers can hijack or block preview access for competing or targeted applications, forcing teams to either downgrade Capgo or work around broken preview functionality. For multi-tenant SaaS operators using Capgo, the cross-tenant nature of the collision creates a secondary risk: a rogue actor might isolate another organization's development team from their preview tools, causing operational friction and potential delays to release cycles.

Affected systems

Capgo versions prior to 12.128.2 are affected. The vulnerability requires the attacker to be an authenticated user of the Capgo platform (PR:L in the CVSS vector), so it is not exploitable by anonymous actors. Any organization running an affected version of Capgo in a multi-tenant or shared preview namespace environment is at risk.

Exploitability

Exploitation requires an active Capgo account (low privilege) and knowledge of a victim's app ID structure. No complex techniques or special conditions are needed—an attacker can register a crafted app ID and trigger preview traffic misdirection. The attack surface is network-accessible and straightforward to execute, though the scope is limited to users of the affected software. The vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog as of the publication date.

Remediation

Organizations using Capgo must upgrade to version 12.128.2 or later. This patch version implements bijective decoding for namespace identifiers, ensuring that no two app IDs—whether using underscores or dots—can collide during preview URL parsing. Verify the specific patch version number and upgrade instructions by consulting the official Capgo release notes.

Patch guidance

Upgrade Capgo to version 12.128.2 or later. This is a straightforward patch release and should be prioritized for any deployment handling multi-tenant or shared preview namespaces. Test the upgrade in a staging environment to confirm preview functionality is restored and no app ID collisions occur. If you are unable to upgrade immediately, isolate preview systems and restrict who can register new app IDs until patching is complete.

Detection guidance

Monitor Capgo logs for unusual preview namespace access patterns, particularly requests that appear to cross between different app IDs or tenants. Look for app IDs registered with underscores that closely resemble existing dotted app IDs in your environment. If possible, audit recent app registrations for anomalous naming that might indicate collision attempts. Check preview traffic routing to see if any legitimate preview requests are being misdirected or denied.

Why prioritize this

Although this vulnerability has a CVSS score of 6.4 (MEDIUM), it should be prioritized based on its cross-tenant impact and the criticality of preview functionality to development workflows. It is not currently on CISA's KEV list, but the ease of exploitation (network-accessible, low-privilege attack) and the direct operational impact on preview access warrant prompt patching. Organizations with heavy reliance on Capgo's preview features or those operating in competitive or sensitive environments should patch sooner rather than later.

Risk score, explained

The CVSS 3.1 score of 6.4 reflects a network-accessible, low-privilege attack with low complexity. The vulnerability causes both integrity impact (misdirected traffic) and availability impact (preview denial), but does not expose confidential data. The score correctly weights the cross-tenant scope (S:C) as a severity multiplier. However, the real-world risk is amplified by the fact that preview environments are integral to development and that an attacker only needs a valid account—making this a notable risk for any Capgo user.

Frequently asked questions

Can an unauthenticated attacker exploit this vulnerability?

No. The CVSS vector includes PR:L (Privileges Required: Low), meaning the attacker must have a valid, authenticated account on the Capgo platform. This limits the attack surface to existing or newly registered users.

Does this vulnerability leak or expose my application code or secrets?

No. The vulnerability causes preview traffic to be misrouted or denied (integrity and availability impacts), but does not directly result in confidentiality breaches. However, denial of preview access can disrupt your development process.

What if I only use Capgo for single-tenant or isolated preview environments?

Your risk is reduced but not eliminated. If your app IDs do not contain dots or you have no competing app IDs with similar naming, the collision risk is lower. However, you should still upgrade to 12.128.2 to close the logical gap and avoid future risk as your app portfolio grows.

Is there a workaround if I cannot upgrade immediately?

Limit who can register new app IDs in your Capgo environment and audit all recent registrations for suspicious names. Avoid using app IDs with underscores that mirror existing dotted app IDs. These are temporary mitigations—upgrade as soon as feasible.

This analysis is provided for informational purposes and reflects publicly available information as of the publication date. Verify all patch versions, upgrade procedures, and vendor advisories directly with Capgo's official documentation. The CVSS score and CWE classification are derived from authoritative sources but should be assessed in the context of your own environment. No liability is assumed for the accuracy or completeness of this analysis. Always test patches in a staging environment before production deployment. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).