Quick answers
- Is CVE-2026-56232 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56232 being exploited in the wild.
- How severe is CVE-2026-56232?
- High severity, with a CVSS score of 8.8, published 24 June 2026.
- Which products and versions are affected?
- Capgo < 12.128.2.
- Is there a fix for CVE-2026-56232?
- 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-56232 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56232?
- 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
An authorization bypass exists in the middlewareKey function within hono_middleware.ts. While the system accepts subkeys via the x-limited-key-id header, it fails to overwrite the 'apikey' context used by downstream route handlers, causing them to default to the unrestricted parent key. Additionally, the middleware lacks a validateSubkeyUser check, which could potentially allow users to reference subkey IDs belonging to other accounts. This allows an authenticated attacker to ignore 'limited_to_orgs' and 'limited_to_apps' constraints, granting full access to all resources associated with the parent API key. The issue is resolved in version 12.128.2.
Affected products
- Capgo Capgo < 12.128.2
Timeline
- 2026-05-07: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD