<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 08:07:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-100623 — Capgo Authentication Bypass via Direct PostgREST org_users Table Write</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-100623</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Cap-go capgo.app&lt;/p&gt;
&lt;p&gt;Capgo (capgo.app) exposes the legacy membership table public.org_users directly through Supabase PostgREST. The table&amp;#39;s row-level security policies &amp;#34;Allow org admin to insert&amp;#34; and &amp;#34;Allow org admin to update&amp;#34; only verify that the caller has admin rights in the target organization (public.check_min_rights(&amp;#39;admin&amp;#39;, ...)); they do not require a pending invitation in tmp_users, acceptance of an invite token via /private/accept_invitation, any action by the target user, or the membership/role-consistency and anti-escalation checks enforced by the RBAC role-binding path. As a result, an authenticated user who is an admin of an organization can INSERT or UPDATE org_users rows directly to add any existing public.users account as an active member of that organization with user_right=&amp;#34;admin&amp;#34;, bypassing the invitation and role-assignment workflow entirely. In testing, an account with no prior access to the organization or its apps could, after such a direct insert, read the organization and app and pass check_min_rights. All versions are affected and no patch was available at the time of publication.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Cap-go capgo.app&lt;/p&gt;
&lt;p&gt;Capgo (capgo.app) exposes the legacy membership table public.org_users directly through Supabase PostgREST. The table&amp;#39;s row-level security policies &amp;#34;Allow org admin to insert&amp;#34; and &amp;#34;Allow org admin to update&amp;#34; only verify that the caller has admin rights in the target organization (public.check_min_rights(&amp;#39;admin&amp;#39;, ...)); they do not require a pending invitation in tmp_users, acceptance of an invite token via /private/accept_invitation, any action by the target user, or the membership/role-consistency and anti-escalation checks enforced by the RBAC role-binding path. As a result, an authenticated user who is an admin of an organization can INSERT or UPDATE org_users rows directly to add any existing public.users account as an active member of that organization with user_right=&amp;#34;admin&amp;#34;, bypassing the invitation and role-assignment workflow entirely. In testing, an account with no prior access to the organization or its apps could, after such a direct insert, read the organization and app and pass check_min_rights. All versions are affected and no patch was available at the time of publication.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-100623</guid>
    </item>
  </channel>
</rss>
