capgo.app before 12.128.12 fails to enforce an organization's API key expiration policy when creating app-scoped API keys. In the POST /apikey endpoint, requests that supply app_id but omit org_id, limited_to_orgs, and expires_at resolve the target app and scope the key to it, but never add the app's owner organization to the list of organization IDs passed to validateExpirationAgainstOrgPolicies; because that list is empty, the validation returns early. As a result, an authenticated organization member can create a non-expiring app-scoped API key even when the owning organization has require_apikey_expiration enabled and a max_apikey_expiration_days limit configured. The issue is fixed in version 12.128.12.
References
Configurations
No configuration.
History
28 Sep 2026, 17:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/Cap-go/capgo.app/security/advisories/GHSA-j6p6-qqcg-3fwp - |
26 Sep 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-26 14:16
Updated : 2026-09-28 20:57
NVD link : CVE-2026-100628
Mitre link : CVE-2026-100628
CVE.ORG link : CVE-2026-100628
JSON object : View
Products Affected
No product.
CWE
CWE-863
Incorrect Authorization
