Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55764

Vulnerability in github.com/klever-io/klever-go (CVE-2026-55764)

Summary

Vulnerability in github.com/klever-io/klever-go (CVE-2026-55764). Risk of unauthorized operations or information disclosure. Exploitable via SFTAddCirculation. Mitigation: upgrade to 1.7.19 or later.

Original description

The description as published by the source.

Summary

On the SFT add-quantity path the only supply bound is SFTAddCirculation, which does
meta.Circulation += amount with no overflow guard, then checks
if meta.Circulation > meta.MaxSupply && meta.MaxSupply != 0. If amount overflows int64 and wraps
negative, negative > MaxSupply is false, the cap check passes, the function returns nil, and the balance
credit stands. A nonce created with a finite MaxSupply (e.g. 1000) can thus be minted to ~MaxInt64 tokens in
one transaction. The fungible mint path is not vulnerable — it has a post-increment MintedValue <= 0 guard
that the SFT path lacks.

Affected code

  • core/kapp/systemAccount/systemAcount.go:132-138 (SFTAddCirculation, the unguarded +=).
  • Caller: core/kapp/kda/mint.go:247-283 (processSemiFungibleAddQuantity); contrast guard mint.go:289.

Impact

A mint-role holder mints ~9.2e18 units of a nonce whose declared MaxSupply is small, with no authorized debit,
and corrupts the on-chain Circulation counter to a negative value (misleading any market/indexer that reads it).

Reachability

Mint-role holder (asset owner or an address granted the role). The mint Amount is a raw int64 from the
contract with no upstream upper bound.

Proof of concept

Unit test

TestExploit_SFTCirculationOverflowBypassesCap creates a nonce capped at MaxSupply = 1000, seeds
Circulation = 5, then calls SFTAddCirculation(MaxInt64). The call returns nil (cap bypassed) and `Circ…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55764 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like SFTAddCirculation over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/klever-io/klever-go to 1.7.19 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-55764" on the vendor's site.

CVE-2026-55764 (github.com/klever-io/klever-go) — CWE-190
Attack surface: SFTAddCirculation / amount / int64 / nil
Patched: 1.7.19 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-190) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via SFTAddCirculation.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: SFTAddCirculation / amount / int64 / nil.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.19.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/klever-io/klever-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/klever-io/klever-go' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/klever-io/klever-go を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/klever-io/klever-go to 1.7.19

    ステージング環境で 1.7.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/klever-io/klever-go
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.19"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details