CVE-2026-100611

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikey_manager organization role may bind to newly created API keys. When an authenticated user holding only apikey_manager (permissions org.manage_apikeys and org.read) calls POST /apikey with a JWT session, the only checks applied are the org.manage_apikeys permission, a fixed deny-list of assignable role names (APIKEY_MANAGER_DENIED_ASSIGNABLE_ROLES in public/apikey/scope.ts), and a priority-rank comparison in createRoleBindingForPrincipal (private/role_bindings.ts). No check verifies that the caller actually holds the permissions conferred by the role being assigned. Because the deny-list omits the deploy roles app_developer, app_uploader, channel_developer and channel_uploader, and apikey_manager is seeded with priority_rank 78 — higher than those roles' ranks (68, 66, 58, 57) — the rank check also passes. As a result, an apikey_manager who cannot upload bundles or promote channels can mint an API key bound to a deploy role and use it to push arbitrary OTA JavaScript updates to all end users of the organization's apps. As of the advisory publication no patched version was available.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
45
EG Risk 45/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Capgo apikey_manager Role Privilege Escalation via Incomplete Role Deny-list | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-apikey-manager-role-privilege-escalation-via-incomplete-role-deny-list
github Patch Available🟡 PoC Available

apikey_manager role can mint OTA-deploy-capable API keys it does not itself hold · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo.app/security/advisories/GHSA-2x4j-p4pr-fvp8

Vendor Advisories for CVE-2026-100611(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 28× 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.

  1. 2026-10-03 18:47 UTCEG score recompute
  2. 2026-10-03 18:47 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-02 18:47 UTCEG score recompute
  5. 2026-10-02 18:47 UTCGHSA enrichment
  6. 2026-10-01 19:49 UTCEPSS rescore
  7. 2026-10-01 18:47 UTCGHSA enrichment
  8. 2026-09-30 18:41 UTCEG score recompute
  9. 2026-09-30 18:41 UTCGHSA enrichment
  10. 2026-09-30 17:38 UTCEG score recompute
  11. 2026-09-30 17:38 UTCGHSA enrichment
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-29 23:48 UTCEG score recompute
  14. 2026-09-29 23:48 UTCGHSA enrichment
  15. 2026-09-29 15:20 UTCEPSS rescore
  16. 2026-09-28 21:14 UTCGHSA enrichment
  17. 2026-09-28 18:21 UTCEG score recompute
  18. 2026-09-28 18:21 UTCGHSA enrichment
  19. 2026-09-28 17:30 UTCEG score recompute
  20. 2026-09-28 17:29 UTCGHSA enrichment
  21. 2026-09-28 14:30 UTCEG score recompute
  22. 2026-09-28 14:30 UTCGHSA enrichment
  23. 2026-09-28 13:50 UTCEPSS rescore
  24. 2026-09-27 14:33 UTCEG score recompute
  25. 2026-09-27 14:33 UTCGHSA enrichment
Show 3 more
  1. 2026-09-26 14:35 UTCEG score recompute
  2. 2026-09-26 13:40 UTCEG score recompute
  3. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100611?
CVE-2026-100611 is a medium vulnerability published on September 26, 2026. Capgo (capgo.app backend, versions ≤ 12.261.0) improperly restricts which roles the apikeymanager organization role may bind to newly created API keys. When an authenticated user holding only apikeymanager (permissions org.manageapikeys and org.read) calls POST /apikey with a JWT session, the only…
When was CVE-2026-100611 disclosed?
CVE-2026-100611 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100611 actively exploited?
CVE-2026-100611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100611?
CVE-2026-100611 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100611?
A fix for CVE-2026-100611 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100611 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100611?

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

Book a Demo →Browse All CVEs