# CVE-2026-100619: Capgo OTA Manifest Poisoning via app_versions.manifest Bypass

> Attackers with write access can poison OTA manifests via a trusted async worker, enabling malicious code execution on client devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-xj78-q428-xww2

## What is CVE-2026-100619?

CVE-2026-100619 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Capgo (capgo.app) blocks direct user inserts into the public.manifest table with a RESTRICTIVE row-level security policy, but that restriction can be bypassed indirectly. A principal holding an app-scoped upload/write/all API key (upload+ rights) or an authenticated user with write+ rights on an app can update public.app_versions.manifest on a version whose storage_provider is 'r2-direct', which is not covered by the bundle content-lock check. The on_version_update async worker trusts record.manifest and, using the service-role Supabase client, inserts the attacker-controlled file_name, file_hash, and s3_path into public.manifest before clearing app_versions.manifest. When a channel points to the crafted version, the /updates endpoint returns the service-role-created manifest entry as a client-facing download_url, enabling OTA manifest poisoning through a trusted async worker path. All versions are affected; no patch was available at the time of publication.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-100619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100619 is a high-severity missing authorization vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100619 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-100619/ (Markdown: https://insights.sbomify.com/CVE-2026-100619/index.md)
```

## Sources

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

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