CVE-2026-56215

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

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

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-20. A secondary CVSS source baseline 8.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 weekElevated
8.3EG
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.4%CVSS: 8.3Exploit: 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.12 as affected, and Capgo versions 12.128.12 as unaffected. No release containing a fix is confirmed on record.

Capgo before 12.128.12 allows authenticated users to modify their mutable public.users.email to arbitrary addresses, which the SSO provisioning endpoint trusts as an account-merge key. Attackers can pre-position their account with a victim's corporate SSO email, causing the provision-user endpoint to merge the victim's SSO identity into the attacker-controlled account.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
53
EG Risk 53/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)
Severity83% × 45%
The EG Score, 8.3 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 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 or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

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 or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the 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 20, 2026

Last Modified

June 24, 2026

Advisory Details (2)

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

Capgo - Account Merge via Poisoned public.users.email in SSO Provisioning | Advisories | VulnCheck

https://www.vulncheck.com/advisories/capgo-account-merge-via-poisoned-public-users-email-in-sso-provisioning
GitHub advisoryMentions a patch (unverified)

User-controlled public.users.email can poison SSO account merge and attach victim SSO identity to attacker account · Advisory · Cap-go/capgo · GitHub

https://github.com/Cap-go/capgo/security/advisories/GHSA-wqc6-fhwf-qpww

Vendor Advisories for CVE-2026-56215(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 13× in last 7d / 36× 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 263 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 163 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56215?
CVE-2026-56215 is a high-severity vulnerability; its CVE record was published on June 20, 2026. Capgo before 12.128.12 allows authenticated users to modify their mutable public.users.email to arbitrary addresses, which the SSO provisioning endpoint trusts as an account-merge key. Attackers can pre-position their account with a victim's corporate SSO email, causing the provision-user endpoint…
When was CVE-2026-56215 made public?
CVE-2026-56215 was made public on May 8, 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 20, 2026. EchelonGraph's copy of the record carries a last-modified date of June 24, 2026; the record at its source may have been updated since.
Is CVE-2026-56215 actively exploited?
CVE-2026-56215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56215?
CVE-2026-56215 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56215?
No fix for CVE-2026-56215 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.12 as affected, and Capgo versions 12.128.12 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-56215 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56215?

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

Book a Demo →Browse All CVEs