# CVE-2026-100616: capgo.app Authentication Bypass via PostgREST customer_id Mutation

> An authenticated organization admin can bypass billing controls by directly modifying the customer_id field via PostgREST, altering subscription status.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-455x-98vm-63r8

## What is CVE-2026-100616?

CVE-2026-100616 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-100616?


## How do I fix CVE-2026-100616?

No fix has been published for CVE-2026-100616 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100616 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100616 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100616 and fix it if it is affected.

What it is: CVE-2026-100616 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100616 exists.

Affected product: Cap-go capgo.app. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100616/ (Markdown: https://insights.sbomify.com/CVE-2026-100616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100616
- OSV: https://osv.dev/vulnerability/CVE-2026-100616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100616/
Summaries are generated and may contain mistakes; the official description above is the record.