Is CVE-2026-47249 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47249 being exploited in the wild.

How severe is CVE-2026-47249?

High severity, with a CVSS score of 7.5, published 7 August 2026.

Which products and versions are affected?

github.com/klever-io/klever-go (Go) < 1.7.18, SEMVER:introduced=0,fixed=1.7.18.

Is there a fix for CVE-2026-47249?

Yes. github.com/klever-io/klever-go (Go): upgrade to 1.7.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47249 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47249?

Check whether you run github.com/klever-io/klever-go (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47249: Klever-io Klever-Go resource exhaustion in P2P resolver

Q: Is there a fix for CVE-2026-47249?

Yes. github.com/klever-io/klever-go (Go): upgrade to 1.7.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47249 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-47249?

Check whether you run github.com/klever-io/klever-go (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47249 · Severity: high · CVSS 7.5 · Published 2026-08-07

Klever-Go is a core component used in the Klever blockchain ecosystem. A vulnerability in how it handles peer-to-peer (P2P) requests allows a remote attacker to send a very small, specially crafted message that consumes a massive amount of memory and processing power on the target server. This can lead to a denial-of-service (DoS) condition, potentially knocking blockchain nodes offline and disrupting the network's availability.

Technologies: github.com/klever-io/klever-go (Go). Vendors: Go.

Quick answers

Is CVE-2026-47249 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47249 being exploited in the wild.
How severe is CVE-2026-47249?: High severity, with a CVSS score of 7.5, published 7 August 2026.
Which products and versions are affected?: github.com/klever-io/klever-go (Go) < 1.7.18, SEMVER:introduced=0,fixed=1.7.18.
Is there a fix for CVE-2026-47249?: Yes. github.com/klever-io/klever-go (Go): upgrade to 1.7.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47249 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47249?: Check whether you run github.com/klever-io/klever-go (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/klever-io/klever-go (Go): upgrade to 1.7.18 or later
```
go get github.com/klever-io/klever-go@v1.7.18
```

Technical details

A resource exhaustion vulnerability (CWE-400) exists in Klever-Go's P2P resolver request handling. The root cause is that the 'Batch.Decompress()' function and subsequent resolver logic (TxResolver and TrieNodeResolver) do not enforce a limit on the number of decoded repeated-field items, even though they enforce a byte-size cap. An attacker can send a compressed 'RequestDataType_HashArrayType' message as small as 442 bytes that expands into 200,000 hash entries upon decompression. This results in significant memory pressure and synchronous CPU work during preallocation and iteration of the decoded hashes. The vulnerability is reachable via libp2p direct-send plumbing and is fixed in version 1.7.18.

Affected products

klever-io klever-go < 1.7.18

Identifiers

CVE-2026-47249
GHSA-w342-mj6g-v9c4
GO-2026-5685

Timeline

2026-06-02: disclosed
2026-06-02: patched: Version 1.7.18 released
2026-06-05: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.