CVE-2026-100624: Capgo.app before 12.264.5 Upload Expiry Bypass via build upload

Severity: medium (CVSS 5.4 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-09-26 · updated 2026-10-05
Weakness: CWE-613

Description

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.

Affected products

Cap-go capgo.app: before 12.264.5 — fixed in 12.264.5

How to fix

Upgrade to a fixed version: Cap-go capgo.app 12.264.5. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-100624 or the next vulnerability affects your stack