Quick answers
- Is CVE-2026-56329 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56329 being exploited in the wild.
- How severe is CVE-2026-56329?
- Medium severity, with a CVSS score of 6.4, published 10 July 2026.
- Which products and versions are affected?
- Capgo < 12.128.2.
- Is there a fix for CVE-2026-56329?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-56329 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56329?
- Check whether you run Capgo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A cross-tenant namespace collision exists in Capgo's preview routing logic due to lossy canonicalization. The preview hostname parser decodes double underscores ('__') into dots ('.') when resolving subdomains, but the application registration logic allows both characters as distinct valid inputs. An attacker with a registered account can create an app ID containing double underscores that resolves to the same preview hostname as a victim's app ID containing dots. This results in an interpretation conflict (CWE-436) where requests for the victim's preview are misrouted to the attacker's application context, leading to a denial of service for the preview functionality. The issue was addressed in version 12.128.2.
Affected products
- Capgo Capgo < 12.128.2
Timeline
- 2026-05-07: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: NVD publication date