Quick answers
- Is CVE-2026-100624 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100624 being exploited in the wild.
- How severe is CVE-2026-100624?
- Medium severity, with a CVSS score of 5.4, published 26 September 2026.
- Which products and versions are affected?
- Capgo.App before 12.264.5.
- Is there a fix for CVE-2026-100624?
- A patch was published on 2026-09-26: fixed in version 12.264.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100624 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-100624?
- Check whether you run Capgo.App at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The /build/upload/:jobId TUS proxy endpoint loads only app_id, owner_org, builder_job_id, and upload_path from the build_requests table, omitting upload_expires_at and status checks before forwarding POST, PATCH, and HEAD requests to the internal builder. An authenticated caller with app.build_native permission can exploit this by sending upload requests after the one-hour upload window expires or after the build transitions to non-pending states (e.g., completed). The vulnerability requires valid API credentials and the appropriate build permission but lacks any time or state validation.
Affected products
- Capgo capgo.app before 12.264.5
Timeline
- 2026-09-26: disclosed
- 2026-09-26: patched: fixed in version 12.264.5