Auth bypass in Cap-Go Capgo.app
CVE-2026-100628
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.
Vulnerability class: Broken Access Control
Published .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/Cap-go/capgo.app/security/advisories/GHSA-j6p6-qqcg-3fwp (vendor-advisory)
- www.vulncheck.com/advisories/capgo-app-before-12.128.12-authentication-bypass-v… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-100628?
- CVE-2026-100628 is a medium-severity vulnerability in Cap-Go Capgo.app, classified under Incorrect Authorization. CVSS score: 4.3/10. Published 2026-09-26.
- How severe is CVE-2026-100628?
- Medium severity. CVSS v3 base score is 4.3 out of 10.