Skip to main content

Threats Tagged 'cve-2026-100616'

View all threats tagged with 'cve-2026-100616'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-100616

Threats Tagged 'cve-2026-100616'

Click on any threat for detailed analysis and mitigation recommendations

A vulnerability in capgo.app's row-level security policy on the public.orgs table allows organization admins with org.update_settings permission to update the entire row, including the internal billing pointer customer_id. This can lead to nullifying or corrupting the Stripe customer pointer, causing billing and plan checks to fail and moving the organization to an unpaid or no-plan state. The official update endpoint restricts edits to certain fields and excludes customer_id, and billing updates require a separate permission. No patch was available at the time of the advisory.

Join the discussion

capgo.app is an over-the-air update platform for Capacitor apps. In all versions prior to a fix, the row-level security UPDATE policy on the public.orgs table permits an organization admin (a user holding org.update_settings) to update the entire row, including the internal billing pointer column customer_id. The official organization update endpoint (supabase/functions/_backend/public/organization/put.ts) allowlists only a small set of editable settings fields and excludes customer_id, and the private Stripe billing route separately requires the org.update_billing permission. By sending an update directly to Supabase PostgREST, an authenticated org admin without org.update_billing can null or corrupt the organization's Stripe customer pointer, causing plan and billing checks that trust orgs.customer_id to fail and moving the organization from a valid paid plan state to unpaid/no-plan behavior. At the time of the advisory no patched version was available.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-100616
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses