Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-cgc5-v3f2-8m2v

Klever: Integer overflow in split-royalty validation enables unbounded minting of KLV (native token)

CVSS 9.6 CriticalCriticalEPSS 0.0056 · 47th percentile

Critical, because:

  • CVSS score 9.6: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 28 Aug 2026, 16:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/klever-io/klever-goGo<1.7.191.7.19
Identifiers
GHSA-cgc5-v3f2-8m2v · CVE-2026-54755 · GO-2026-6310
Weakness (CWE)
CWE-190
Tags
Published
28 Aug 2026
Updated
2 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Klever node (github.com/klever-io/klever-go) versions before 1.7.19 are vulnerable. The split-royalty percentages of a KDA asset are summed into a 32-bit integer without a per-entry bound, so two entries can wrap the sum to a value that passes validation. A user who can create an asset and make a transfer can then mint KLV, the native token, without limit. Upgrade to version 1.7.19 or later. The source gives few details on any workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.6 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0056, the 47th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:47 UTC First seen by agentprime
  2. 31 Oct 2026, 14:47 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.