CVE-2026-100624
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 12% of all known CVEs.
References
Related Vulnerabilities
Other CWE-613 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-2595 | Critical | 9.8 | 17% | - | - |
| CVE-2023-30403 | High | 7.5 | 14% | - | - |
| CVE-2020-27422 | Critical | 9.8 | 7.9% | - | - |
| CVE-2014-3616 | Medium | 4.3 | 5.7% | - | Fix |
| CVE-2021-3144 | Critical | 9.1 | 5.1% | - | Fix |
| CVE-2021-24019 | High | 8.1 | 3.9% | - | Fix |
Common questions
How do I fix CVE-2026-100624?
No published fix for CVE-2026-100624 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-100624 being actively exploited?
Not that we know of. CVE-2026-100624 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.22% is the estimated probability that it will be exploited in the next 30 days. That is higher than 12% of all scored CVEs.
How severe is CVE-2026-100624?
CVE-2026-100624 has a CVSS v3 base score of 5.4, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-100624
Markdown
[](https://tridentstack.com/cve/CVE-2026-100624)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100624"><img src="https://tridentstack.com/cve/badge/CVE-2026-100624.svg" alt="CVE-2026-100624"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-05.