CVE-2026-100628
mediumcapgo.app before 12.128.12 fails to enforce an organization's API key expiration policy when creating app-scoped API keys.
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/Cap-go/capgo.app/security/advisories/GHSA-j6p6-qqcg-3fwp disclosure@vulncheck.com
- https://www.vulncheck.com/advisories/capgo-app-before-12.128.12-authentication-bypass-via-... disclosure@vulncheck.com
- https://github.com/Cap-go/capgo.app/security/advisories/GHSA-j6p6-qqcg-3fwp 134c704f-9b21-4f2e-91b3-4a467353bcc0