Quick answers
- Is CVE-2026-56240 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56240 being exploited in the wild.
- How severe is CVE-2026-56240?
- Medium severity, with a CVSS score of 4.3, published 11 July 2026.
- Which products and versions are affected?
- Capgo < 12.128.12.
- Is there a fix for CVE-2026-56240?
- 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-56240 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56240?
- 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 billing authorization bypass exists in Capgo due to a logic divergence between the plugin hot-path 'plan_valid' expression and the authoritative billing gate. The 'plan_valid' check incorrectly relies on the 'orgs.has_usage_credits' flag, which only indicates if a credit grant record exists, rather than verifying if the credits are unexpired or have a positive balance. An authenticated attacker with an exhausted or expired credit grant can exploit this to maintain access to restricted endpoints including /updates, /stats, /channel_self, and attachment uploads. The issue was addressed in version 12.128.12 by ensuring the validation logic correctly checks for available, unexpired credits.
Affected products
- Capgo Capgo < 12.128.12
Timeline
- 2026-05-08: advisory: GitHub Security Advisory published
- 2026-07-11: disclosed: NVD publication date