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.
References
Configurations
No configuration.
History
28 Sep 2026, 18:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/Cap-go/capgo.app/security/advisories/GHSA-443r-w5p8-rhr2 - |
26 Sep 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-26 14:16
Updated : 2026-09-30 18:18
NVD link : CVE-2026-100619
Mitre link : CVE-2026-100619
CVE.ORG link : CVE-2026-100619
JSON object : View
Products Affected
No product.
CWE
CWE-266
Incorrect Privilege Assignment
