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-100628 Overview
Capgo.app versions before 12.128.12 contain an authorization flaw [CWE-863] in the POST /apikey endpoint. The endpoint fails to enforce an organization's API key expiration policy when creating app-scoped API keys. An authenticated organization member can create a non-expiring API key even when the owning organization has require_apikey_expiration enabled with a max_apikey_expiration_days limit. The vulnerability stems from an empty organization list being passed to the validateExpirationAgainstOrgPolicies function, causing validation to return early. Capgo fixed the issue in version 12.128.12.
Critical Impact
Authenticated organization members can bypass expiration policies to create persistent API keys, undermining credential lifecycle controls and increasing the window for credential abuse.
Affected Products
- capgo.app versions prior to 12.128.12
Discovery Timeline
- 2026-09-26 - CVE-2026-100628 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100628
Vulnerability Analysis
The flaw resides in the POST /apikey endpoint responsible for creating API keys. When a request supplies app_id but omits org_id, limited_to_orgs, and expires_at, the endpoint resolves the target application and scopes the new key to it. However, the handler never adds the app's owner organization to the list of organization IDs forwarded to validateExpirationAgainstOrgPolicies.
Because the validation routine receives an empty list, it returns early without evaluating any expiration constraints. The result is a successful key creation that silently ignores the owning organization's require_apikey_expiration flag and max_apikey_expiration_days limit. This is a broken authorization condition classified as [CWE-863] Incorrect Authorization.
Root Cause
The root cause is incomplete scope resolution before policy enforcement. The code path infers organization ownership from app_id for the purpose of scoping the key, but it does not reuse that ownership information when assembling the organization list passed to the expiration validator. The validator treats an empty organization list as a no-op, so no policy ever applies to the request.
Attack Vector
Exploitation requires an authenticated account that is a member of the target organization. The attacker sends a crafted POST /apikey request containing only app_id, deliberately omitting org_id, limited_to_orgs, and expires_at. The server returns an app-scoped API key with no expiration, which the attacker can retain indefinitely for access to the application's data and functions.
The vulnerability requires no user interaction and no elevated privileges beyond standard organization membership. For technical details, see the GitHub Security Advisory GHSA-j6p6-qqcg-3fwp and the VulnCheck Advisory on Authentication Bypass.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-100628
Indicators of Compromise
- API keys created through POST /apikey with a null or absent expires_at value in environments where require_apikey_expiration is enabled.
- Audit records showing API key creation requests that include app_id but omit org_id and limited_to_orgs.
- Long-lived app-scoped API keys associated with organizations that enforce a max_apikey_expiration_days cap.
Detection Strategies
- Query the API key store for keys created before upgrading to 12.128.12 that have no expiration and are scoped only to an app_id.
- Correlate API key creation events with the requesting user's organization role to identify members creating non-expiring keys.
- Review web server and application logs for POST /apikey requests whose body contains app_id without the companion scoping fields.
Monitoring Recommendations
- Alert on any newly minted API key whose expiration is null when the owning organization has an expiration policy configured.
- Track usage patterns of app-scoped API keys and flag keys that remain active beyond the organization's configured maximum lifetime.
- Monitor administrative changes to require_apikey_expiration and max_apikey_expiration_days to detect attempts to mask policy violations.
How to Mitigate CVE-2026-100628
Immediate Actions Required
- Upgrade capgo.app to version 12.128.12 or later.
- Enumerate existing API keys and revoke any non-expiring app-scoped keys that violate current organization expiration policies.
- Rotate credentials for applications whose API keys may have been created through the vulnerable code path.
Patch Information
The issue is fixed in capgo.app version 12.128.12. The patch ensures that the app's owner organization is included in the organization list passed to validateExpirationAgainstOrgPolicies, so expiration policies are evaluated for every app-scoped key creation request. Refer to the GitHub Security Advisory GHSA-j6p6-qqcg-3fwp for release details.
Workarounds
- Restrict API key creation privileges to a reduced set of trusted organization administrators until the upgrade is complete.
- Implement server-side or proxy-level request inspection to reject POST /apikey requests that omit org_id and expires_at.
- Periodically audit the key store and revoke any keys that lack an expiration timestamp.
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

