<?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://cve.radiocsirt.org</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, 05 Oct 2026 18:16:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-88863 — capgo.app through 12.207.1 Privilege Escalation via invite_new_user_to_org</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-88863</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Cap-go capgo.app&lt;/p&gt;
&lt;p&gt;capgo.app (npm package `capgo`) through version 12.207.1 does not compare the caller&amp;#39;s role rank against the requested role in the validateInvite() function of supabase/functions/_backend/private/invite_new_user_to_org.ts. The POST /private/invite_new_user_to_org endpoint only requires the org.update_user_roles permission for org_super_admin invitations, so an authenticated user holding only the org.invite_user permission (e.g., an org_member) can invite an external user as org_admin or org_billing_admin. When the invited account accepts the invitation via POST /private/accept_invitation, ensureOrgMembership creates the role binding using the Supabase service-role key, which bypasses the prevent_role_binding_priority_escalation and check_org_user_privileges database triggers. This allows privilege escalation resulting in full administrative control over the organization&amp;#39;s apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter&amp;#39;s rank before permitting elevated invitations.&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.app (npm package `capgo`) through version 12.207.1 does not compare the caller&amp;#39;s role rank against the requested role in the validateInvite() function of supabase/functions/_backend/private/invite_new_user_to_org.ts. The POST /private/invite_new_user_to_org endpoint only requires the org.update_user_roles permission for org_super_admin invitations, so an authenticated user holding only the org.invite_user permission (e.g., an org_member) can invite an external user as org_admin or org_billing_admin. When the invited account accepts the invitation via POST /private/accept_invitation, ensureOrgMembership creates the role binding using the Supabase service-role key, which bypasses the prevent_role_binding_priority_escalation and check_org_user_privileges database triggers. This allows privilege escalation resulting in full administrative control over the organization&amp;#39;s apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter&amp;#39;s rank before permitting elevated invitations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-88863</guid>
    </item>
  </channel>
</rss>
