CVE-2026-100624: medium-severity vulnerability in Cap-go capgo.app
Capgo.app before 12.264.5 Upload Expiry Bypass via build upload
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.3%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Affected products
Cap-go · capgo.appRelated CVEs — Cap-go capgo.app
In the same product, most dangerous first.
CVE-2026-88861HIGHCapgo AAL1 Session MFA Bypass via Direct RBAC AuthorizationEPSS 0.5%CVE-2026-88862HIGHCapgo API Key Manager Authentication Bypass via x-limited-key-idEPSS 0.4%CVE-2026-100622HIGHcapgo.app through 12.129.0 Cache Restoration of Deleted BundlesEPSS 0.4%CVE-2026-100623HIGHCapgo Authentication Bypass via Direct PostgREST org_users Table WriteEPSS 0.4%CVE-2026-100619HIGHCapgo OTA Manifest Poisoning via app_versions.manifest BypassEPSS 0.4%CVE-2026-100614HIGHCapgo before 12.244.1 Cross-Tenant Image Overwrite via Metadata WorkerEPSS 0.4%