HighGHSA-w24w-wp77-qffmCVE-2023-34451GO-2023-1883

CometBFT may duplicate transactions in the mempool's data structures

Published 5 Jul 2023 · Updated 10 Sept 2026

Is your project on an affected github.com/cometbft/cometbft?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<0.34.29
Fixed in
0.34.29
Update to the fixed version for your release line, for example:go get github.com/cometbft/cometbft@v0.34.29
Affected
>=0.37.0 <0.37.2
Fixed in
0.37.2
Update to the fixed version for your release line, for example:go get github.com/cometbft/cometbft@v0.37.2

Details

Impact

The mempool maintains two data structures to keep track of outstanding transactions: a list and a map. These two data structures are supposed to be in sync all the time in the sense that the map tracks the index (if any) of the transaction in the list.

Unfortunately, it is possible to have them out of sync. When this happens, the list may contain several copies of the same transaction. Because the map tracks a single index, it is then no longer possible to remove all the copies of the transaction from the list. This happens even if the duplicated transaction is later committed in a block. The only way to remove the transaction is by restarting the node.

These are the steps to cause the above duplication problem. Everything should happen within one height, that is no FinalizeBlock or BeginBlock ABCI calls should happen while these steps are reproduced:

1. send transaction tx1 to the target full node via RPC 2. send N more different transactions to the target full node, where N should be higher than the node's configured value for cache_size in config.toml 3. send transaction tx1 again to the target full node

One of the copies of tx1 is now _stuck_ in the mempool's data structures. Effectively causing a memory leak, and having that node gossiping that transaction to its peers forever.

The above problem can be repeated on and on until a sizable number of transactions are stuck in the mempool, in order to try to bring down the target node.

This problem is present in releases: v0.37.0, and v0.37.1, as well as in v0.34.28, and all previous releases of the CometBFT repo. It will be fixed in releases v0.34.29 and v0.37.2.

Patches

The PR containing the fix is here.

Workarounds

  • Increasing the value of cache_size in config.toml makes it very difficult to effectively attack a full node.
  • Not exposing the transaction submission RPC's would mitigate the probability of a successful attack, as the attacker would then have to create a modified (byzantine) full node to be able to perform the attack via p2p.

References

  • PR that introduced the map to track transactions in the mempool.
  • PR containing the fix.

Is GHSA-w24w-wp77-qffm in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cometbft/cometbft, and gives you the command that fixes it.

More advisories for github.com/cometbft/cometbft

  • LowGO-2026-4361Inconsistencies between how commit signatures are verified and how block time is derived in github.com/cometbft/cometbft · 19 Feb 2026
  • HighGHSA-c32p-wcqj-j677CometBFT has inconsistencies between how commit signatures are verified and how block time is derived · 23 Jan 2026
  • LowGO-2025-4025CometBFT's invalid BitArray handling can lead to network halt in github.com/cometbft/cometbft · 18 Nov 2025
  • HighGHSA-hrhf-2vcr-ghchCometBFT's invalid BitArray handling can lead to network halt · 14 Oct 2025
  • LowCVE-2025-24371CometBFT allows a malicious peer to make node stuck in blocksync in github.com/cometbft/cometbft · 4 Feb 2025
  • LowGO-2025-3443CometBFT allows a malicious peer to stall network by disseminating valid-looking block parts in github.com/cometbft/cometbft · 4 Feb 2025
All 21 advisories for github.com/cometbft/cometbft

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.