Capgo Broken Object Level Authorization via x-limited-key-id Header

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: VulnCheck

Description

Capgo before 12.128.2 contains a broken object level authorization vulnerability in middlewareKey() that accepts the client-controlled x-limited-key-id header without validating ownership, allowing authenticated users to adopt cross-tenant limited keys. Attackers can supply another tenant's limited key ID to bypass authorization checks and access unauthorized cross-tenant resources across multiple API endpoints.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-30

Last Modified

2026-06-30

Generated

2026-07-01

AI Q&A

2026-07-01

EPSS Evaluated

N/A

NVD

CVE-2026-56230

EUVD

EUVD-2026-40427

Affected Vendors & Products

Vendor	Product	Version / Range
capgo	capgo	to 12.128.2 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

This vulnerability exists in Capgo versions before 12.128.2 and involves broken object level authorization in the middlewareKey() function. The function accepts a client-controlled header called x-limited-key-id without verifying if the user owns that key. This flaw allows authenticated users to use limited keys belonging to other tenants, effectively bypassing authorization checks and gaining access to unauthorized resources across multiple API endpoints.

Impact Analysis

The vulnerability can lead to unauthorized access to resources belonging to other tenants. Attackers who are authenticated can supply another tenant's limited key ID to bypass authorization controls, potentially exposing sensitive data or functionality that should be restricted. This can result in data breaches, loss of confidentiality, and unauthorized actions within the affected system.

Hi! I’m here to help you understand CVE-2026-56230. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70