CVE Catalog

CVE-2026-100628

MediumCVSS 4.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.20%

9th percentile - higher than 9% of all known CVEs

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 passed to validateExpirationAgainstOrgPolicies, allowing an authenticated organization member to create a non-expiring app-scoped API key.

Risk Assessment

Even when an organization has require_apikey_expiration enabled and a max_apikey_expiration_days limit configured, a non-expiring API key can be created. Long-lived keys increase the risk of unauthorized access if leaked.

Recommendation

Update capgo.app to version 12.128.12 or later. Until the update, monitor created API keys and manually remove those without an expiration date.

Other vulnerabilities in Capgo

See all
Original NVD description (English source)

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 data from NVD (NIST) · CISA KEV · EPSS