https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 08:30:29 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-366277 EUVD-2026-366277 https://cve.radiocsirt.org/vuln/euvd-2026-366277 https://cve.radiocsirt.org/vuln/fkie_cve-2026-88863 <p>capgo.app (npm package `capgo`) through version 12.207.1 does not compare the caller&#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&#39;s apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter&#39;s rank before permitting elevated invitations.</p> <p>capgo.app (npm package `capgo`) through version 12.207.1 does not compare the caller&#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&#39;s apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter&#39;s rank before permitting elevated invitations.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-88863 https://cve.radiocsirt.org/vuln/ghsa-9758-4f33-587j <p>capgo.app (npm package `capgo`) through version 12.207.1 does not compare the caller&#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&#39;s apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter&#39;s rank before permitting elevated invitations.</p> <p>capgo.app (npm package `capgo`) through version 12.207.1 does not compare the caller&#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&#39;s apps, channels, members, and billing. The issue is addressed by pull request #3096, which compares the inviter&#39;s rank before permitting elevated invitations.</p> https://cve.radiocsirt.org/vuln/ghsa-9758-4f33-587j