# 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.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-mqr8-g67p-jm26, GHSA-r6v6-qvq3-q232

## 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 (DEPRECATED: Insufficient Session Expiration)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100624 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100624 exists.

Affected product: Cap-go capgo.app. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100624/ (Markdown: https://insights.sbomify.com/CVE-2026-100624/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100624
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100624
- OSV: https://osv.dev/vulnerability/CVE-2026-100624

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100624/
Summaries are generated and may contain mistakes; the official description above is the record.