CVE-2026-56231

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-38738 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists Capgo versions before 12.128.2 as affected, and Capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

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.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Cross-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-hfrg
Web page

Capgo - 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-parameter

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 172 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 17:44 UTCEG score recompute
  2. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-25 14:18 UTCEG score recompute
  6. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-19 14:02 UTCEG score recompute
  13. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-18 03:29 UTCEG score recompute
  15. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-12 15:40 UTCEG score recompute
  22. 2026-10-11 19:38 UTCEG score recompute
  23. 2026-10-11 16:53 UTCEG score recompute
  24. 2026-10-11 14:16 UTCEG score recompute
  25. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 75 more
  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-09-23 11:49 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-09-18 08:14 UTCEG score recompute
  22. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  26. 2026-09-14 01:58 UTCEG score recompute
  27. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  28. 2026-09-13 12:11 UTCEG score recompute
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-08-30 20:21 UTCEG score recompute
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-08-28 04:51 UTCEG score recompute
  43. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-08-25 01:09 UTCEG score recompute
  47. 2026-08-24 13:48 UTCEG score recompute
  48. 2026-08-23 00:57 UTCEG score recompute
  49. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  50. 2026-08-22 13:18 UTCEG score recompute
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  52. 2026-08-21 06:19 UTCEG score recompute
  53. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  54. 2026-08-20 07:36 UTCEG score recompute
  55. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-08-19 02:20 UTCEG score recompute
  57. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  58. 2026-08-17 14:03 UTCEG score recompute
  59. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  60. 2026-08-16 15:20 UTCEG score recompute
  61. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  62. 2026-08-16 03:58 UTCEG score recompute
  63. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  64. 2026-08-15 05:14 UTCEG score recompute
  65. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  66. 2026-08-14 06:31 UTCEG score recompute
  67. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  68. 2026-08-12 19:52 UTCEG score recompute
  69. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  70. 2026-08-11 21:08 UTCEG score recompute
  71. 2026-08-11 09:47 UTCEG score recompute
  72. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  73. 2026-08-09 23:40 UTCEG score recompute
  74. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  75. 2026-08-09 00:57 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56231?
CVE-2026-56231 is a high-severity vulnerability; its CVE record was published on June 24, 2026. 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 appid supplied in the request body and never verify that the…
When was CVE-2026-56231 made public?
CVE-2026-56231 was made public on March 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 24, 2026. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56231 actively exploited?
CVE-2026-56231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56231?
CVE-2026-56231 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56231?
No fix for CVE-2026-56231 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists Capgo versions before 12.128.2 as affected, and Capgo versions 12.128.2 as unaffected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56231

Explore →

Is Your Infrastructure Affected by CVE-2026-56231?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs