Vulnerability in Capgo.app (CVE-2026-100624)
Summary
Vulnerability in Capgo.app (CVE-2026-100624). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 12.264.5 or later.
Original description
The description as published by the source.
Capgo.app before 12.264.5 does not enforce upload expiry or build lifecycle state in the /build/upload/:jobId TUS proxy endpoint. When a native build request is created, an upload_expires_at timestamp (one hour) and a 'pending' status are stored in build_requests, but the upload proxy loads only app_id, owner_org, builder_job_id, and upload_path and checks only the app.build_native permission before forwarding POST, PATCH, and HEAD requests to the internal builder. As a result, an authenticated caller holding app.build_native permission for the app can continue writing to the build upload session after the stored expiry has passed or after the build has moved beyond the upload phase, unless the separate builder service independently rejects the request. The issue is fixed in 12.264.5.
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-100624 has been found in Capgo.app.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Capgo.app to 12.264.5 or later.
If unsure, ask your IT team or search "Capgo.app CVE-2026-100624" on the vendor's site.
CVE-2026-100624 (Capgo.app) — CWE-613 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 12.264.5 — apply immediately
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-613) exists in Capgo.app.
Check the vendor advisory for the affected versions of Capgo.app.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 12.264.5.
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.app' . 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.app' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Capgo.appを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Capgo.app to 12.264.5ステージング環境で 12.264.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com