CVE-2026-52879

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-05. A secondary CVSS source baseline 7.5; 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

Also known asEUVD-2026-54720 (ENISA EUVD) · GHSA-hf2g-6j7h-98wg (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate 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.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttler, or bound on the number of concurrent in-flight spawns. Because the antiflood check runs inside the spawned goroutine rather than before it, a single connected peer can open a direct-send stream and send a stream of well-formed messages to force unbounded goroutine creation, where each goroutine allocates its own stack and holds a message reference until processing completes, adding scheduler and garbage-collection pressure faster than the runtime can drain it. This lets one peer degrade the node's availability and its ability to process legitimate traffic, resulting in a remotely triggerable denial of service. The issue is fixed in 1.7.18.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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.
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 public PoC (CISA Vulnrichment) · Automatable yes (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
42nd
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 5, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: github_release, github.
GitHub release Patch Available

v1.7.18 - Coordinated Security Release

Patch available: klever-io/klever-go v1.7.18

https://github.com/klever-io/klever-go/releases/tag/v1.7.18
GitHub advisoryMentions a patch (unverified)

klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg

Vendor Advisories for CVE-2026-52879(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/klever-io/klever-go @ 1.7.18 (fixes >= 1.7.14, <= 1.7.17)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/klever-io/klever-go—
  • 1.7.14 up to 1.7.18: fixed in 1.7.18
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 112 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 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-52879?
CVE-2026-52879 is a high-severity vulnerability; its CVE record was published on June 5, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttler,…
When was the CVE record for CVE-2026-52879 published?
The CVE record for CVE-2026-52879 was published on June 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-52879 actively exploited?
CVE-2026-52879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52879?
CVE-2026-52879 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52879?
A fix for CVE-2026-52879 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52879 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52879

Explore →

Is Your Infrastructure Affected by CVE-2026-52879?

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

Book a Demo →Browse All CVEs