CVE-2026-100628
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Summary
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Cap-go | capgo.app | 0 < 12.128.12 | affected |
| Cap-go | capgo.app | 12.128.12 | unaffected |
Weaknesses
- CWE-863: Incorrect Authorization
References
- https://github.com/Cap-go/capgo.app/security/advisories/GHSA-j6p6-qqcg-3fwp
- https://www.vulncheck.com/advisories/capgo-app-before-12.128.12-authentication-bypass-via-apikey
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.