Skip to content

CVE-2026-56232

Incorrect Authorization: is CVE-2026-56232real, exploitable, or a false positive? Here's the community verdict.

High · CVSS 8.8CWE-863 · Incorrect Authorization

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Capgo before 12.128.2 fails to enforce limited_to_orgs and limited_to_apps 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.

Published

Embed this verdict
TruePositive verdict for CVE-2026-56232
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-56232/badge.svg)](https://www.truepositive.app/cve/CVE-2026-56232)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-56232"><img src="https://www.truepositive.app/cve/CVE-2026-56232/badge.svg" alt="TruePositive verdict for CVE-2026-56232"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

In your experience, is this finding real and exploitable?

0 verdicts
Not a real issue

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

No notes yet. Be the first to share what you saw, or a fix that worked.

    Add a field note or remediationoptional
    Note type

    What are you adding?

    Markdown supported · minimum 20 characters.

    Same weakness: CWE-863 · Incorrect Authorization.