8.8
HIGH CVSS 3.1
CVE-2026-56230
Capgo - Broken Object Level Authorization via x-limited-key-id Header
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.

INFO

Published Date :

June 30, 2026, 10:08 p.m.

Last Modified :

June 30, 2026, 10:08 p.m.

Remotely Exploit :

Yes !

Source :

VulnCheck
Affected Products

The following products are affected by CVE-2026-56230 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH 83251b91-4cc7-4094-a5c7-464a1b83ea10
CVSS 4.0 HIGH 83251b91-4cc7-4094-a5c7-464a1b83ea10
Solution
Update Capgo to version 12.128.2 or later to fix broken object level authorization.
  • Update Capgo to version 12.128.2 or later.
  • Validate ownership of x-limited-key-id header.
  • Implement stricter authorization checks for cross-tenant access.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-56230 vulnerability anywhere in the article.

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.