CVE-2026-100624 Capgo.app before 12.264.5 Upload Expiry Bypass via build upload
Authenticated users with build permissions can bypass upload expiry checks to modify build sessions after expiration, potentially altering build artifacts.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-100624?
CVE-2026-100624 is a medium-severity vulnerability in Cap-go capgo.app, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-613
Which versions are affected by CVE-2026-100624?
How do I fix CVE-2026-100624?
No fix has been published for CVE-2026-100624 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-100624 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100624 exists.
Sources
Also known as GHSA-mqr8-g67p-jm26, GHSA-r6v6-qvq3-q232.