Capgo before 12.128.2 contains a broken object level authorization (BOLA) vulnerability in the POST /build/start/:jobId and POST /build/cancel/:jobId endpoints. The handlers authorize the request based only on the attacker-controlled app_id supplied in the request body and never verify that the jobId in the URL belongs to that app_id (or the same tenant/org) before issuing privileged builder commands with the server-held builder API key. An authenticated user with the app.build_native permission for any app they control can start or cancel arbitrary builder jobs belonging to other tenants by supplying a victim jobId, resulting in cross-tenant build sabotage (denial of service), unauthorized compute actions, and potential billing impact.
CVE-2026-56231
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(medium)
- EPSS
- 7.3%
- KEV
- Not listed
Published
June 24, 2026
Last Modified
June 25, 2026
Advisory Details (2)
Auto-updated Jun 25, 2026Cross-tenant build job control (cancel/start) via jobId parameter enables build sabotage (BOLA) · Advisory · Cap-go/capgo · GitHub
https://github.com/Cap-go/capgo/security/advisories/GHSA-72j4-9qp5-hfrgCapgo - Broken Object Level Authorization in Build Job Control via jobId Parameter | Advisories | VulnCheck
https://www.vulncheck.com/advisories/capgo-broken-object-level-authorization-in-build-job-control-via-jobid-parameterWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 63× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 17:49 UTCEG score recompute
- 2026-07-12 06:26 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 18:50 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 07:28 UTCEG score recompute
- 2026-07-10 20:06 UTCEG score recompute
- 2026-07-10 08:42 UTCEG score recompute
- 2026-07-09 21:19 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 09:57 UTCEG score recompute
- 2026-07-08 22:34 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 11:13 UTCEG score recompute
- 2026-07-07 23:50 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 12:29 UTCEG score recompute
- 2026-07-07 01:02 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 13:40 UTCEG score recompute
Show 38 moreShow fewer
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:15 UTCEG score recompute
- 2026-07-05 14:54 UTCEG score recompute
- 2026-07-05 03:26 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 16:04 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:41 UTCEG score recompute
- 2026-07-03 17:20 UTCEG score recompute
- 2026-07-03 05:58 UTCEG score recompute
- 2026-07-02 18:34 UTCEG score recompute
- 2026-07-02 07:12 UTCEG score recompute
- 2026-07-01 19:51 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 08:30 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 21:08 UTCEG score recompute
- 2026-06-30 09:45 UTCEG score recompute
- 2026-06-29 22:22 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 11:00 UTCEG score recompute
- 2026-06-28 23:38 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 12:16 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 00:53 UTCEG score recompute
- 2026-06-27 13:31 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 02:09 UTCEG score recompute
- 2026-06-26 14:46 UTCEG score recompute
- 2026-06-26 03:11 UTCEG score recompute
- 2026-06-25 15:48 UTCEG score recompute
- 2026-06-25 15:47 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-285
Frequently asked(5)
What is CVE-2026-56231?
When was CVE-2026-56231 disclosed?
Is CVE-2026-56231 actively exploited?
What is the CVSS score of CVE-2026-56231?
How do I remediate CVE-2026-56231?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56231
Is Your Infrastructure Affected by CVE-2026-56231?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.