Vulnerability in github.com/klever-io/klever-go (CVE-2026-47249)
Summary
Vulnerability in github.com/klever-io/klever-go (CVE-2026-47249). Risk of unauthorized operations or information disclosure. Exploitable via RequestDataType_HashArrayType. Mitigation: upgrade to 1.7.18 or later.
Original description
The description as published by the source.
Summary
A connected peer can send a compressed RequestDataType_HashArrayType direct request that is only 442 bytes on the wire but expands into 200000 decoded hash entries inside the resolver path. On klever-go v1.7.17, this allows remote memory and CPU amplification against nodes that accept P2P peer connections.
Details
Resolver antiflood logic accounts only one logical message and the compressed wire size in data/retriever/resolvers/messageProcessor.go#L30.
Batch.Decompress() in data/batch/batch.go#L122 enforces an inflated byte cap but does not enforce a decoded repeated-field item cap. After decompression, TxResolver preallocates and iterates all decoded hashes in data/retriever/resolvers/transactionResolver.go#L194, and TrieNodeResolver iterates the same unchecked decoded set in data/retriever/resolvers/trieNodeResolver.go#L108.
Pinned references:
- https://github.com/klever-io/klever-go/blob/333f6ec910906e227705fc5767dc897d8fbfc862/data/retriever/resolvers/messageProcessor.go#L30
- https://github.com/klever-io/klever-go/blob/333f6ec910906e227705fc5767dc897d8fbfc862/data/batch/batch.go#L122
- https://github.com/klever-io/klever-go/blob/333f6ec910906e227705fc5767dc897d8fbfc862/data/retriever/resolvers/transactionResolver.go#L194
- https://github.com/klever-io/klever-go/blob/333f6ec910906e227705fc5767dc897d8fbfc862/data/retriever/resolvers/trieNodeResolver.go#L108
This appears distinct from the public CVE-2026-44697 / `GHSA-87m7-qffr-…
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-47249 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like RequestDataType_HashArrayType 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-47249" on the vendor's site.
CVE-2026-47249 (github.com/klever-io/klever-go) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: RequestDataType_HashArrayType / TxResolver / TrieNodeResolver / MultiDataInterceptor
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-400) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via RequestDataType_HashArrayType without authentication.
Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: RequestDataType_HashArrayType / TxResolver / TrieNodeResolver / MultiDataInterceptor.
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 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
-
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/klever-io/klever-go to 1.7.18ステージング環境で 1.7.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web github.com