Vulnerability in github.com/klever-io/klever-go (CVE-2026-52878)
Summary
Vulnerability in github.com/klever-io/klever-go (CVE-2026-52878). Risk of unauthorized operations or information disclosure. Exploitable via POST /transaction/send. Mitigation: upgrade to 1.7.18 or later.
Original description
The description as published by the source.
Summary
Every transaction gossiped on the klever-go P2P network is decoded and validated
synchronously inside the libp2p pubsub topic-validator callback. The validator
txVersionChecker.CheckTxVersion dereferences tx.RawData.Version with no nil
check. A protobuf Transaction whose embedded RawData sub-message is omitted
decodes to RawData == nil, so validating it triggers a nil-pointer panic.
The libp2p pubsub callback, the underlying go-libp2p-pubsub validation worker, and
klever's own network/p2p layer install no recover(), so the panic propagates and
crashes the entire node process. The attacker payload is a 3-byte protobuf message;
no validator key, stake, funds, or on-chain account is required. Aimed at enough of
the BLS validator set, repeated delivery halts block production (chain halt).
Affected component
- Root cause:
core/versioning/txVersionChecker.go:22 - Reached via:
core/process/transaction/interceptedTransaction.go:203(integrity) and:154(CheckValidity) - Production tx-topic path:
core/process/interceptors/multiDataInterceptor.go:171and:223 - Unprotected caller:
network/p2p/libp2p/netMessenger.gopubsubCallback(no recover) - Topic wiring:
core/process/factory/interceptorscontainer/baseInterceptorsContainerFactory.go(createOneTxInterceptor)
Details
Synchronous validation path, no recovery at any frame:
libp2p pubsubCallback network/p2p/libp2p/netMessenger.go (no recover)
-> Multi…
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-52878 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like POST /transaction/send over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/klever-io/klever-go to 1.7.18 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-52878" on the vendor's site.
CVE-2026-52878 (github.com/klever-io/klever-go) — CWE-476 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /transaction/send / txVersionChecker.CheckTxVersion / tx.RawData.Version / Transaction
Patched: 1.7.18 — 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.
A vulnerability (CWE-476) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via POST /transaction/send without authentication.
Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: POST /transaction/send / txVersionChecker.CheckTxVersion / tx.RawData.Version / Transaction.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.7.18.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /transaction/send requests with malformed payloads or SQL meta-characters. 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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /transaction/send' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /transaction/sendへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/klever-io/klever-go to 1.7.18ステージング環境で 1.7.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /transaction/send on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web security-advisories@github.com
- web github.com