Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100623 Overview
CVE-2026-100623 is an authorization bypass vulnerability in Capgo (capgo.app), a live-update platform for Capacitor applications. The flaw exposes the legacy membership table public.org_users directly through Supabase PostgREST. Row-level security (RLS) policies validate only that the caller holds admin rights in the target organization. They skip the invitation workflow, the role-binding path, and the anti-escalation checks enforced by the RBAC layer. An authenticated organization admin can insert or update rows in org_users to add any existing public.users account as an active admin member. All versions are affected and no patch was available at the time of publication. The weakness is tracked under [CWE-863: Incorrect Authorization].
Critical Impact
Any authenticated organization admin can silently add arbitrary existing Capgo accounts as admin members of their organization, bypassing invitation acceptance and granting full read access to organization data, apps, and check_min_rights protected operations.
Affected Products
- Capgo (capgo.app) - all versions
- Supabase PostgREST-exposed public.org_users table
- Capgo RBAC role-binding workflow
Discovery Timeline
- 2026-09-26 - CVE CVE-2026-100623 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-100623
Vulnerability Analysis
The vulnerability stems from permissive RLS policies on the legacy public.org_users membership table. Capgo exposes this table directly through Supabase PostgREST, allowing authenticated clients to issue INSERT and UPDATE statements against it. The policies Allow org admin to insert and Allow org admin to update call public.check_min_rights('admin', ...) and nothing else. They do not validate that a pending invitation exists in tmp_users. They do not require an invite token to be accepted through /private/accept_invitation. They do not demand any action by the target user, and they skip the membership and role-consistency validation that the RBAC role-binding path enforces. An admin can therefore write directly to the table and attach any existing user account as an active member with user_right="admin". In testing, an account with no prior access to the organization or its apps could read the organization and app and pass check_min_rights immediately after the direct insert.
Root Cause
The root cause is incomplete authorization logic in the RLS policies protecting org_users. The policies treat organization admin status as sufficient to add members, but the application's documented membership flow depends on invitation acceptance and anti-escalation checks that live outside RLS. Exposing the raw table through PostgREST allows clients to bypass the server-side workflow that would normally enforce those controls.
Attack Vector
An attacker needs valid credentials for any Capgo account that holds admin rights in at least one organization. The attacker sends an authenticated PostgREST request to insert or update rows in org_users, specifying the user_id of any existing public.users account and setting user_right to admin. The target user receives no invitation, no notification, and takes no action. After the write, the added account passes check_min_rights and can read organization resources and apps.
No verified exploit code is published. See the GitHub Security Advisory GHSA-w349-9mc3-8c5x and the VulnCheck Advisory for the full technical write-up.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-100623
Indicators of Compromise
- Rows in public.org_users whose creation does not correlate with a matching accepted entry in tmp_users or an /private/accept_invitation call.
- Membership records added for user accounts that have no prior login, app, or organization interaction history.
- Sudden appearance of multiple user_right="admin" entries added by the same actor within a short time window.
Detection Strategies
- Query public.org_users and join against invitation records in tmp_users to surface memberships created without an invitation lifecycle.
- Review PostgREST request logs for direct INSERT and UPDATE operations targeting the org_users endpoint, especially those bypassing the standard RBAC role-binding API.
- Correlate new organization memberships with authentication activity for the newly added user to detect members who were added but never signed in through the invitation flow.
Monitoring Recommendations
- Alert on any change to the user_right column in org_users where the previous value is null or where no corresponding invitation record exists.
- Audit Supabase service logs for high-volume membership mutations originating from a single authenticated session.
- Track read access by newly added members to organization and app resources and flag access that begins within seconds of the membership insert.
How to Mitigate CVE-2026-100623
Immediate Actions Required
- Restrict PostgREST access to public.org_users by revoking the table from the authenticated role and routing all membership changes through a security-definer function that enforces the invitation workflow.
- Audit the current contents of org_users and remove members whose addition cannot be tied to an accepted invitation or legitimate RBAC role-binding event.
- Rotate credentials for organization admin accounts if evidence of unauthorized membership writes is found.
Patch Information
No patch was available at the time of publication. Monitor the GitHub Security Advisory GHSA-w349-9mc3-8c5x for upstream fixes and apply the vendor's remediation guidance as soon as it is released.
Workarounds
- Replace the Allow org admin to insert and Allow org admin to update RLS policies with policies that additionally require a matching accepted invitation in tmp_users for the target user_id.
- Disable direct PostgREST write access to org_users and force membership changes through the RBAC role-binding path that performs role-consistency and anti-escalation checks.
- Add database triggers on org_users that reject INSERT or UPDATE operations when no corresponding invitation acceptance record exists.
# Configuration example
# Revoke direct write access to the legacy membership table
REVOKE INSERT, UPDATE ON public.org_users FROM authenticated;
# Drop the permissive policies
DROP POLICY "Allow org admin to insert" ON public.org_users;
DROP POLICY "Allow org admin to update" ON public.org_users;
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

