PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-56225 Capgo CVE debrief

CVE-2026-56225 is an authorization bypass vulnerability in Capgo's public API key management handlers (get/put/delete/post). API keys created with mode=all but restricted to a single app via limited_to_apps are only checked for limited_to_orgs and not for limited_to_apps, allowing an app-scoped key to enumerate, update, and delete sibling API keys belonging to the same account that are outside its declared app scope. This enables tampering with account-level credentials. The vulnerability has a CVSS score of 8.7 and is classified as HIGH severity. The CVE was published on 2026-06-23T13:16:44.250Z and last modified on 2026-06-23T14:52:58.543Z.

Vendor
Capgo
Product
Unknown
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-23
Original CVE updated
2026-06-23
Advisory published
2026-06-23
Advisory updated
2026-06-23

Who should care

Organizations using Capgo's API key management system should be aware of this vulnerability and take immediate action to mitigate the risk. The vulnerability allows an attacker to tamper with account-level credentials, potentially leading to unauthorized access and data breaches. Security teams and administrators responsible for managing API keys and credentials should prioritize patching and updating their systems.

Technical summary

The vulnerability is caused by a lack of proper authorization checks in Capgo's API key management handlers. Specifically, API keys created with mode=all but restricted to a single app via limited_to_apps are not properly validated, allowing an app-scoped key to access and manipulate sibling API keys outside its declared app scope. This is due to the fact that the system only checks for limited_to_orgs and not for limited_to_apps. As a result, an attacker with an app-scoped key can enumerate, update, and delete API keys belonging to the same account, potentially leading to account-level credential tampering.

Defensive priority

High priority should be given to patching and updating Capgo's API key management system to prevent exploitation of this vulnerability. Security teams should also review and monitor API key usage to detect potential suspicious activity.

Recommended defensive actions

  • Apply the patch or update to version 12.128.2 or later
  • Review and monitor API key usage for suspicious activity
  • Implement additional security controls, such as multi-factor authentication and access restrictions
  • Conduct a thorough review of API key management policies and procedures
  • Consider implementing compensating controls, such as API key rotation and revocation

Evidence notes

The CVE record and NVD detail provide official information about the vulnerability. The source item URL provides additional context and references. The GitHub security advisory and Vulncheck advisory provide detailed information about the vulnerability and its impact.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-56225 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-56225

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-56225 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-56225

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.