CVE-2026-88860

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.3Exploit: None knownExposed services: Not assessed

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

Capgo fails to clean up channel permission overrides when a user's last organization role binding is deleted, leaving stale overrides active. Attackers can retain channel-specific permissions after their base RBAC access has been revoked to perform unauthorized actions like changing production OTA versions.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

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 (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

September 10, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 10, 2026
No fix on record yet. Sources: github.
Web page

Capgo Authorization Bypass via Stale Channel Permission Overrides | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-authorization-bypass-via-stale-channel-permission-overrides
GitHub advisoryMentions a patch (unverified)

Deleting a user's last org role binding leaves channel permission overrides active, allowing continued OTA release selection · Advisory · Cap-go/capgo.app · GitHub

https://github.com/Cap-go/capgo.app/security/advisories/GHSA-qfxq-2ch8-hjg9

Vendor Advisories for CVE-2026-88860(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 24× in last 7d / 93× 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.

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. 1 repeat row among the latest 100 is merged into the row it repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88860?
CVE-2026-88860 is a medium-severity vulnerability; its CVE record was published on September 10, 2026. Capgo fails to clean up channel permission overrides when a user's last organization role binding is deleted, leaving stale overrides active. Attackers can retain channel-specific permissions after their base RBAC access has been revoked to perform unauthorized actions like changing production OTA…
When was CVE-2026-88860 made public?
CVE-2026-88860 was made public on August 27, 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 September 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-88860 actively exploited?
CVE-2026-88860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88860?
CVE-2026-88860 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-88860?
No fix for CVE-2026-88860 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-88860 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-88860?

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

Book a Demo →Browse All CVEs