---
id: CVE-2026-100621
title: >-
  Capgo (capgo.app) contains an incomplete access-control/content-lock
  enforcement issue affecting all versions; no patch is available at the time of
  publication
summary: >-
  Capgo (capgo.app) contains an incomplete access-control/content-lock
  enforcement issue affecting all versions; no patch is available at the time of
  publication. The `enforce_encrypted_bundle_trigger` /
  `check_encrypted_bundle_on_insert` …
severity: medium
cvss: 4.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'
cwe:
  - CWE-284
vendor: Cap-go
product: capgo.app
affected:
  - capgo.app
published: '2026-09-26'
updated: '2026-09-26'
sourceUpdated: '2026-09-26T14:16:43.017'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100621'
references:
  - url: >-
      https://github.com/Cap-go/capgo.app/security/advisories/GHSA-5rg9-rhwj-wj76
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/capgo-app-content-lock-bypass-via-r2-direct-bundle-mutation
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-26T13:33:20.929Z'
---

## Overview

Capgo (capgo.app) contains an incomplete access-control/content-lock enforcement issue affecting all versions; no patch is available at the time of publication. The `enforce_encrypted_bundle_trigger` / `check_encrypted_bundle_on_insert` content lock in supabase/schemas/prod.sql exempts `app_versions` rows whose previous `storage_provider` is `r2-direct`, so delivery-critical columns (name, app_id, session_key, key_id, storage_provider, r2_path, external_url, checksum, manifest, native_packages) remain mutable while a row is in that state. Separately, the channel/version join used by the `/updates` endpoint (supabase/functions/_backend/utils/pg.ts) filters only deleted versions and does not exclude `r2-direct` versions, so such rows remain OTA-selectable. An attacker holding a Capgo API key with bundle write/upload permission can create or keep a bundle version in the `r2-direct` state, assign it to a channel, and then modify these fields via direct PostgREST requests, causing altered bundle metadata (for example checksum and session_key) to be served to devices through `/updates`. This bypasses the post-upload content immutability hardening added for a previous app_versions metadata-tampering issue.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.