CVE-2026-56247

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. A secondary CVSS source baseline 8.8; 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 weekElevated
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.4%CVSS: 8.8Exploit: 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 allows org admins to assign org-scoped RBAC roles at app scope without validating role scope compatibility, including to pending invitees. Attackers can pre-seed malformed high-privilege bindings that survive invite acceptance, enabling accepted low-privilege users to perform unauthorized privileged app actions.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 public PoC (CISA Vulnrichment) · Automatable no (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)14 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 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

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (2)

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

Org admins can assign org-level RBAC roles at app scope, including to pending invitees, leading to end-to-end privilege escalation after invite acceptance · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-55q2-p3m2-x66x
Web page

Capgo - Privilege Escalation via Cross-Scope RBAC Role Assignment | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-privilege-escalation-via-cross-scope-rbac-role-assignment

Vendor Advisories for CVE-2026-56247(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 12× in last 7d / 37× 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 243 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 143 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56247?
CVE-2026-56247 is a high-severity vulnerability; its CVE record was published on July 1, 2026. Capgo before 12.128.2 allows org admins to assign org-scoped RBAC roles at app scope without validating role scope compatibility, including to pending invitees. Attackers can pre-seed malformed high-privilege bindings that survive invite acceptance, enabling accepted low-privilege users to perform…
When was CVE-2026-56247 made public?
CVE-2026-56247 was made public on May 7, 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 July 1, 2026. EchelonGraph's copy of the record carries a last-modified date of July 1, 2026; the record at its source may have been updated since.
Is CVE-2026-56247 actively exploited?
CVE-2026-56247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56247?
CVE-2026-56247 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56247?
No fix for CVE-2026-56247 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 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. The vendor advisories EchelonGraph has for CVE-2026-56247 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56247?

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

Book a Demo →Browse All CVEs