Quick answers
- Is CVE-2026-56237 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56237 being exploited in the wild.
- How severe is CVE-2026-56237?
- Critical severity, with a CVSS score of 9.1, published 24 June 2026.
- Which products and versions are affected?
- Capgo < 12.128.2.
- Is there a fix for CVE-2026-56237?
- 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-56237 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56237?
- 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 broken authentication vulnerability exists in Capgo's API key generation mechanism due to improper server-side validation and client-side exposure of key parameters. The application allows the frontend to specify the API key value during the generation request, and the backend fails to verify if the key was securely generated or bound to the requesting user. An attacker can intercept the generation request and replace the key parameter with an arbitrary value (e.g., a custom numeric string). Because the backend accepts these user-supplied values without validation, an attacker can effectively create valid, custom API keys to bypass authentication and access protected endpoints. The issue is resolved in version 12.128.2 by moving key generation entirely to the server side.
Affected products
- Capgo Capgo < 12.128.2
Timeline
- 2026-02-10: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: NVD publication date