CVE-2026-56213Medium· 5.3▾ TwilightPoC availableCapgo before 12.128.2 contains an authorization bypass vulnerability in the public.upsert_version_meta SECURITY DEFINER function exposed via PostgREST RPC, allowing unauthenticated attackers to insert arbitrary rows into version_meta for…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 29.2 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.4%
Capgo before 12.128.2 contains an authorization bypass vulnerability in the public.upsert_version_meta SECURITY DEFINER function exposed via PostgREST RPC, allowing unauthenticated attackers to insert arbitrary rows into version_meta for any app_id. Attackers can exploit this by calling the RPC endpoint with a public anon key to poison storage metrics, causing persistent false data in dashboards and triggering incorrect alerts across victim applications.
Capgo < 12.128.2Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-56073Critical· 9.4Cap-go - OTP Bypass via Response Manipulation in Email Verification
CVE-2026-56080Medium· 4.9Cap-go - Authentication Logic Flaw in Enforce Password Policy
CVE-2026-56081Critical· 9.1Cap-go - Account Lockout via 2FA Misconfiguration on Unverified Email
CVE-2026-56079Medium· 6.5Capgo - Cross-Tenant Authorization Bypass via PostgREST Webhook Access
CVE-2026-56082High· 7.5Capgo - Unauthenticated Cross-Tenant Billing Log Tampering via public.record_build_time RPC
CVE-2026-56215High· 8.3Capgo - Account Merge via Poisoned public.users.email in SSO Provisioning