Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100615 Overview
CVE-2026-100615 is a privilege escalation vulnerability in Cap-go capgo.app affecting versions before 12.267.1. The flaw resides in the API key rotation endpoint, which fails to validate the privilege level of the target key before performing a rotation. An authenticated user holding the apikey_manager role can enumerate sibling keys owned by the same organization and rotate a higher-privileged org_super_admin key through the PUT endpoint. The server returns the replacement plaintext secret, enabling the attacker to authenticate as the higher-privileged principal. The weakness is categorized as [CWE-269] Improper Privilege Management.
Critical Impact
An apikey_manager can escalate to org_super_admin by rotating a sibling key and recovering its plaintext credential from the API response.
Affected Products
- Cap-go capgo.app versions prior to 12.267.1
Discovery Timeline
- 2026-09-26 - CVE-2026-100615 published to the National Vulnerability Database (NVD)
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100615
Vulnerability Analysis
The vulnerability exists in the API key management workflow of capgo.app. The rotation endpoint accepts a key identifier and issues a new secret for that key without comparing the privilege level of the caller to the privilege level of the target key. Because the response body contains the newly generated plaintext secret, the rotating principal immediately obtains credentials for whichever key was rotated.
This is a horizontal-and-vertical access control failure. The apikey_manager role is designed to manage keys at an administrative tier below org_super_admin, but the authorization check treats all keys owned by the same organization as rotatable by any key manager. The result is a direct path from mid-tier management to full organizational administration.
Root Cause
The root cause is missing privilege validation on the target object during a privileged action. The rotation handler authorizes the caller's ability to perform rotations in general, rather than authorizing the caller against the specific role attached to the key being rotated. There is no role-tier comparison between the acting principal and the target key.
Attack Vector
The attack is executed remotely over the network and requires only authenticated access with the apikey_manager role. An attacker enumerates API keys belonging to the same organization owner, identifies a key bound to org_super_admin, and submits a rotation request through the vulnerable PUT endpoint. The service responds with the new plaintext secret, which the attacker then uses to authenticate as org_super_admin. No user interaction is required and no additional exploitation primitives are needed.
Technical details are available in the GitHub Security Advisory GHSA-8h52-44r7-w343 and the VulnCheck Advisory on Privilege Escalation.
Detection Methods for CVE-2026-100615
Indicators of Compromise
- PUT requests to the API key rotation endpoint originating from accounts bound to the apikey_manager role but targeting key identifiers associated with org_super_admin.
- Successful authentications using API keys whose last rotation timestamp was initiated by a lower-privileged principal within the same organization.
- Short time windows in which an apikey_manager session enumerates organization keys and then issues a rotation call against a sibling key.
Detection Strategies
- Correlate API audit logs to flag rotation events where the acting user's role is lower than the role attached to the rotated key.
- Alert on sequences of GET /apikeys enumeration followed by PUT /apikeys/{id} operations from the same session.
- Baseline rotation frequency per key and alert on unexpected out-of-band rotations of administrative keys.
Monitoring Recommendations
- Forward capgo.app application and access logs to a centralized logging platform and retain rotation events for forensic review.
- Monitor for first-use of newly rotated API keys from source addresses not previously associated with the owning principal.
- Track role-to-role actions and alert when a privilege boundary is crossed by a management operation.
How to Mitigate CVE-2026-100615
Immediate Actions Required
- Upgrade Cap-go capgo.app to version 12.267.1 or later.
- Audit all API keys and rotate any org_super_admin keys that may have been exposed, especially those rotated by apikey_manager principals.
- Review the audit history of the API key rotation endpoint for unauthorized rotations prior to patching.
Patch Information
The issue is fixed in Cap-go capgo.app version 12.267.1. Refer to the GitHub Security Advisory GHSA-8h52-44r7-w343 for upgrade guidance and patch details.
Workarounds
- Restrict assignment of the apikey_manager role to a minimum set of trusted operators until the patch is applied.
- Temporarily revoke the apikey_manager role for non-essential accounts and require elevated administrators to perform key rotations.
- Segregate org_super_admin keys into separate organizations where feasible so they cannot be enumerated as siblings by lower-tier managers.
# Verify the installed version meets the patched baseline
npm list @capgo/capgo.app
# Expected: @capgo/capgo.app@12.267.1 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

