CVE-2026-100628 capgo.app before 12.128.12 Authentication Bypass via apikey
Authenticated users can bypass API key expiration policies to create non-expiring keys, undermining security controls in Capgo.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-100628?
CVE-2026-100628 is a high-severity authentication bypass vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-863
Which versions are affected by CVE-2026-100628?
How do I fix CVE-2026-100628?
No fix has been published for CVE-2026-100628 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-100628 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100628 exists.
Sources
Also known as GHSA-38jp-2fr7-m68g, GHSA-j6p6-qqcg-3fwp.