CVE-2025-24371: GO-2025-3442 - CometBFT allows a malicious peer to make node stuck in blocksync in github.com/cometbft/cometbft

CVE-2025-24371 · Severity: medium · CVSS 4 · Published 2025-02-04

CometBFT allows a malicious peer to make node stuck in blocksync in github.com/cometbft/cometbft

Technologies: github.com/cometbft/cometbft (Go). Vendors: Go.

Quick answers

Is CVE-2025-24371 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-24371 being exploited in the wild.
How severe is CVE-2025-24371?
Medium severity, with a CVSS score of 4, published 4 February 2025.
Which products and versions are affected?
github.com/cometbft/cometbft (Go) SEMVER:introduced=0,fixed=0.38.17, SEMVER:introduced=1.0.0-alpha.1,fixed=1.0.1.
Is there a fix for CVE-2025-24371?
Yes. github.com/cometbft/cometbft (Go): upgrade to 0.38.17, 1.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-24371?
Check whether you run github.com/cometbft/cometbft (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/cometbft/cometbft (Go): upgrade to 0.38.17, 1.0.1 or later
    go get github.com/cometbft/cometbft@v1.0.1

Affected products

  • github.com/cometbft/cometbft (Go) SEMVER:introduced=0,fixed=0.38.17, SEMVER:introduced=1.0.0-alpha.1,fixed=1.0.1

Identifiers

  • CVE-2025-24371
  • GHSA-22qq-3xwm-r5x4
  • GO-2025-3442

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