CVE-2026-88864 Capgo SSO Provider Authentication Bypass via PostgREST Direct Write
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: total
Description
Capgo (capgo.app) fails to restrict direct write access to the public.sso_providers table exposed through Supabase PostgREST. A holder of an ordinary Capgo full API key can insert a row with status='active' and enforce_sso=true, bypassing the intended backend SSO provisioning route (supabase/functions/_backend/private/sso/providers.ts) and its controls: the Enterprise plan requirement, SSO provider creation via the Supabase Management API, DNS TXT domain-ownership verification, the pending_verification → verified → active status transition, and issuance of a trusted provider ID by Supabase Auth. The forged row is trusted by SSO discovery and enforcement logic, including the unauthenticated login preflight endpoint /private/sso/check-domain, which then reports {"has_sso": true, "enforce_sso": true} for domains that were never verified, allowing attacker-controlled SSO enforcement to be asserted for arbitrary domains and disrupting normal login. All versions are affected; at the time of the advisory no patch was available.
Upgrade path
1 package: 0 fixed, 1 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| Cap-go capgo.app | All versions | No fix listed | No fix yet |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Cap-go capgo.app | All versions | No fix listed |
References
- GitHub Security Advisory (GHSA-xg7v-83qv-qfff) exploit vendor-advisory
- VulnCheck Advisory: Capgo SSO Provider Authentication Bypass via PostgREST Direct Write third-party-advisory
- ENISA EUVD EUVD-2026-75414 third-party-advisory