CVE-2026-47249

HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Klever-Go KVM: Hash-array amplification in P2P resolver request handling

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-542v, which covered MultiDataInterceptor compressed batch fan-in. This report concerns resolver request paths that remain reachable through real libp2p direct-send plumbing on v1.7.17.

PoC

Reproduced with:

go run auditpoc/request_batch_hash_amplification_poc.go
go test github.com/klever-io/klever-go/auditpoc -run TestRequestBatchHashAmplification_DirectSendReachability -count=1

Observed output:

request wire bytes: 442
fits direct-send limit (983040 bytes): true
tx resolver lookups: 200000
trie resolver lookups: 200000
heap delta before first tx lookup: 17.47 MiB
ok   github.com/klever-io/klever-go/auditpoc

The E2E harness registers the victim resolver on the request topic and sends the malicious payload through SendToConnectedPeer() to prove the work amplification survives the real direct-send path.

Impact

A connected peer can convert a sub-kilobyte request into large decode-time memory pressure and synchronous CPU work on the target node. Repeated requests or several concurrent peers can degrade or exhaust validator resources, affecting node availability.

CVSS v3
7.5
EG Score
7.5(low)
EPSS
16.0%
KEV
Not listed

Published

June 5, 2026

Last Modified

June 5, 2026

Vendor Advisories for CVE-2026-47249(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/klever-io/klever-go—1.7.18—

Data Freshness Timeline

(refreshed 10× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-05 18:35 UTCEG score recompute
  2. 2026-07-04 20:45 UTCEG score recompute
  3. 2026-07-03 21:21 UTCEG score recompute
  4. 2026-07-03 09:48 UTCEG score recompute
  5. 2026-07-02 16:44 UTCEG score recompute
  6. 2026-07-02 05:29 UTCEG score recompute
  7. 2026-07-01 18:24 UTCEG score recompute
  8. 2026-07-01 07:17 UTCEG score recompute
  9. 2026-06-30 18:56 UTCEG score recompute
  10. 2026-06-30 07:51 UTCEG score recompute
  11. 2026-06-29 19:38 UTCEG score recompute
  12. 2026-06-29 08:32 UTCEG score recompute
  13. 2026-06-28 20:32 UTCEG score recompute
  14. 2026-06-28 09:27 UTCEG score recompute
  15. 2026-06-27 22:22 UTCEG score recompute
  16. 2026-06-27 11:16 UTCEG score recompute
  17. 2026-06-27 00:09 UTCEG score recompute
  18. 2026-06-26 13:03 UTCEG score recompute
  19. 2026-06-25 19:47 UTCEG score recompute
  20. 2026-06-25 08:41 UTCEG score recompute
  21. 2026-06-24 21:36 UTCEG score recompute
  22. 2026-06-24 08:29 UTCEG score recompute
  23. 2026-06-23 17:37 UTCEG score recompute
  24. 2026-06-23 01:49 UTCEG score recompute
  25. 2026-06-22 14:41 UTCEG score recompute
Show 36 more
  1. 2026-06-21 05:21 UTCEG score recompute
  2. 2026-06-20 08:35 UTCEG score recompute
  3. 2026-06-19 15:07 UTCEG score recompute
  4. 2026-06-19 03:31 UTCEG score recompute
  5. 2026-06-18 16:12 UTCEG score recompute
  6. 2026-06-18 04:21 UTCEG score recompute
  7. 2026-06-17 17:15 UTCEG score recompute
  8. 2026-06-17 05:43 UTCEG score recompute
  9. 2026-06-16 18:38 UTCEG score recompute
  10. 2026-06-16 07:21 UTCEG score recompute
  11. 2026-06-15 20:15 UTCEG score recompute
  12. 2026-06-15 09:10 UTCEG score recompute
  13. 2026-06-14 23:18 UTCEPSS rescore
  14. 2026-06-14 22:00 UTCEG score recompute
  15. 2026-06-14 10:53 UTCEG score recompute
  16. 2026-06-13 23:48 UTCEG score recompute
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-13 12:44 UTCEG score recompute
  19. 2026-06-13 01:35 UTCEG score recompute
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 14:30 UTCEG score recompute
  22. 2026-06-12 03:24 UTCEG score recompute
  23. 2026-06-11 16:20 UTCEG score recompute
  24. 2026-06-11 05:01 UTCEG score recompute
  25. 2026-06-10 17:56 UTCEG score recompute
  26. 2026-06-10 06:51 UTCEG score recompute
  27. 2026-06-09 19:46 UTCEG score recompute
  28. 2026-06-09 08:41 UTCEG score recompute
  29. 2026-06-08 21:36 UTCEG score recompute
  30. 2026-06-08 10:28 UTCEG score recompute
  31. 2026-06-07 23:23 UTCEG score recompute
  32. 2026-06-07 12:18 UTCEG score recompute
  33. 2026-06-07 01:13 UTCEG score recompute
  34. 2026-06-06 14:07 UTCEG score recompute
  35. 2026-06-06 03:02 UTCEG score recompute
  36. 2026-06-05 15:57 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47249?
CVE-2026-47249 is a high vulnerability published on June 5, 2026. Klever-Go KVM: Hash-array amplification in P2P resolver request handling 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…
When was CVE-2026-47249 disclosed?
CVE-2026-47249 was first published in the National Vulnerability Database on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47249 actively exploited?
CVE-2026-47249 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47249?
CVE-2026-47249 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-47249?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47249, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47249

Explore →

Is Your Infrastructure Affected by CVE-2026-47249?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs