Quick answers
- Is CVE-2026-56252 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56252 being exploited in the wild.
- How severe is CVE-2026-56252?
- Medium severity, with a CVSS score of 5.4, published 12 July 2026.
- Which products and versions are affected?
- Capgo < 12.128.2.
- Is there a fix for CVE-2026-56252?
- 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-56252 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56252?
- 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 scope isolation vulnerability exists in Capgo's webhook testing functionality due to incorrect authorization logic in the `apikeyHasOrgRight()` function. The `POST /webhooks/test` endpoint fails to enforce the `limited_to_apps` restriction when validating API keys, only checking if the key has organization-level rights or if `limited_to_orgs` is empty. An authenticated attacker with a low-privileged, app-scoped API key can bypass these checks to trigger signed outbound webhook deliveries for any webhook within their organization. This allows for unauthorized interaction with downstream integrations and access to delivery metadata. The issue is addressed in version 12.128.2.
Affected products
- Capgo Capgo < 12.128.2
Timeline
- 2026-05-07: advisory: GitHub Security Advisory published
- 2026-07-12: disclosed: NVD publication date