CVE-2025-24371General

LOWCVSS 7.1 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

CometBFT is a distributed, Byzantine fault-tolerant, deterministic state machine replication engine. In the `blocksync` protocol peers send their `base` and `latest` heights when they connect to a new node (`A`), which is syncing to the tip of a network. `base` acts as a lower ground and informs `A` that the peer only has blocks starting from height `base`. `latest` height informs `A` about the latest block in a network. Normally, nodes would only report increasing heights. If `B` fails to provide the latest block, `B` is removed and the `latest` height (target height) is recalculated based on other nodes `latest` heights. The existing code however doesn't check for the case where `B` first reports `latest` height `X` and immediately after height `Y`, where `X > Y`. `A` will be trying to catch up to 2000 indefinitely. This condition requires the introduction of malicious code in the full node first reporting some non-existing `latest` height, then reporting lower `latest` height and nodes which are syncing using `blocksync` protocol. This issue has been patched in versions 1.0.1 and 0.38.17 and all users are advised to upgrade. Operators may attempt to ban malicious peers from the network as a workaround.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-703

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • General: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-04-21: 204-21
Signal classification1 categories
General
2100.0%
Referenced assets1 URL
By indicator
Full discourse2 posts
  • Doyeon Park@p6rkdoye0n
    General

    @PerkinsFund It was documented with reference to a CVE that has the same impact. please review it https://www.cve.org/CVERecord?id=CVE-2025-24371

    Post summary

    The tweet merely references CVE-2025-24371 without providing any technical details, proof‑of‑concept, exploit code, or patch information.

    100401.4K
    752 followersView on X
  • Doyeon Park@p6rkdoye0n
    General

    @eternalsakura13 @l33d0hyun but there is already a CVE recorded for a bug with the same impact that occurred in the same component. CVE-2025-24371 (https://www.cve.org/CVERecord?id=CVE-2025-24371)

    Post summary

    The user merely points out that a CVE (CVE-2025-24371) already exists for a similar bug, providing only the CVE reference.

    00011437
    767 followersView on X

Explore more