# CVE-2026-56229: Capgo - Cross-App Build Job Access via app_id/job_id Mismatch in /build/status and /build/logs

> Attackers can access build logs and metadata from other applications by mismatching app and job IDs, exposing sensitive information.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 21 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-2fw5-mcrx-wcqw, GHSA-fp2v-g9f3-6fwg

## What is CVE-2026-56229?

CVE-2026-56229 is a high-severity missing authorization vulnerability in Capgo, published on 21 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Capgo before 12.128.2 contains an authorization bypass vulnerability in the /build/status and /build/logs endpoints that allows attackers to access build jobs belonging to different applications by supplying a mismatched app_id and job_id combination. Limited API keys restricted to a single app can retrieve build status and logs from other apps by providing an authorized app_id while using a job_id from an unauthorized app, exposing sensitive build information including logs, metadata, and potentially credentials.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-56229?


## How do I fix CVE-2026-56229?

No fix has been published for CVE-2026-56229 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56229 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56229 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56229 is a high-severity missing authorization vulnerability in Capgo, published on 21 Jun 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-56229 exists.

Affected product: Capgo. 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-56229/ (Markdown: https://insights.sbomify.com/CVE-2026-56229/index.md)
```

## Sources

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

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