Vulnerability in Capgo (CVE-2026-100621)
Summary
Vulnerability in Capgo (CVE-2026-100621). Risk of unauthorized operations or information disclosure. Exploitable via enforce_encrypted_bundle_trigger.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-100621 has been found in Capgo.
Attackers can target a specific entry point like enforce_encrypted_bundle_trigger over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Capgo CVE-2026-100621" on the vendor's site.
CVE-2026-100621 (Capgo) — CWE-284 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: enforce_encrypted_bundle_trigger / check_encrypted_bundle_on_insert / app_versions / storage_provider
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in Capgo. Attackers reach the vulnerable code path via enforce_encrypted_bundle_trigger.
Check the vendor advisory for the affected versions of Capgo. Attack surface: enforce_encrypted_bundle_trigger / check_encrypted_bundle_on_insert / app_versions / storage_provider.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Capgo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Capgo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Capgoを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com