CVE-2026-100628

published 26 Sep 2026 · updated 28 Sep 2026

capgo.app before 12.128.12 Authentication Bypass via apikey

4.3MediumCVSS 4.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 12.128.12.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Cap-go<12.128.1212.128.12

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-100628 severity on Zeptric[![CVE-2026-100628](https://zeptric.io/badge/cve/CVE-2026-100628.svg)](https://zeptric.io/cve/CVE-2026-100628)