CVE-2026-56232: Capgo - Subkey Scope Bypass in middlewareKey via x-limited-key-id Header
Capgo before 12.128.2 fails to enforce limitedtoorgs and limitedtoapps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the unrestricted parent key instead of the scoped subkey.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Capgo - middlewareKey (subkey scope bypass via x-limited-key-id)to a version that resolves this vulnerability.Fixed in 12.128.2 - Compensating control
Until upgraded, do not allow clients to supply or control the x-limited-key-id header used by the middlewareKey function; block or strip the x-limited-key-id header at the edge (e.g., reverse proxy/WAF) so scoped subkeys cannot be bypassed.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-56232?
The severity of CVE-2026-56232 is high with a CVSS score of 8.8.
How do I fix CVE-2026-56232?
To fix CVE-2026-56232, update Capgo to version 12.128.2 or later.
What vulnerability does CVE-2026-56232 expose in the Capgo software?
CVE-2026-56232 exposes a subkey scope bypass vulnerability in the middlewareKey function.
Who is affected by CVE-2026-56232?
Any user of Capgo versions prior to 12.128.2 is affected by CVE-2026-56232.
What can an attacker do with CVE-2026-56232?
An attacker can bypass subkey scope restrictions using their own subkeys, leading to unauthorized access to downstream route handlers.