GHSA-hrhf-2vcr-ghch: CometBFT's invalid BitArray handling can lead to network halt
Name: ASA-2025-003: Invalid BitArray handling can lead to network halt Criticality: High (Considerable Impact; Possible Likelihood per ACMv1.2) Affected versions: <= v0.38.18, <= v0.37.15, and main development branches Affected users: Validators, Full nodes, Users Description A bug was discovered in CometBFT's handling of BitArray's that have a mismatch between the BitArray's expected number of Elems for the…
Published Oct 14, 2025
Affected packages
github.com/cometbft/cometbft
- Ecosystem
- Go
- Affected
- <= 0.37.15
- Fixed in
- 0.37.16
- Check
go list -m github.com/cometbft/cometbft
github.com/cometbft/cometbft
- Ecosystem
- Go
- Affected
- >= 0.38.0-alpha.1, <= 0.38.18
- Fixed in
- 0.38.19
- Check
go list -m github.com/cometbft/cometbft
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Name: ASA-2025-003: Invalid BitArray handling can lead to network halt Criticality: High (Considerable Impact; Possible Likelihood per ACMv1.2) Affected versions: <= v0.38.18, <= v0.37.15, and main development branches Affected users: Validators, Full nodes, Users
Description
A bug was discovered in CometBFT's handling of BitArray's that have a mismatch between the BitArray's expected number of Elems for the specified number of Bits. Additional validation was added to prevent processing BitArray's in this invalid state, as well as guards to prevent panics on BitArray methods if one of these invalid states is processed.
Impact
BitArray's are present in a number of messages received from peers. When handling these messages, insufficient validation was applied to prevent processing messages the aforementioned invalid state. In the worst case, nodes will gossip messages to peers in an invalid state before processing them themselves, leading to a network halt (instead of only the node receiving the malicious message crashing).
Patches
The new CometBFT releases v0.38.19 and v0.37.16 fix this issue.
Unreleased code in the main branch is patched as well.
Workarounds
If a node is able to identify a malicious peer sending these payloads, they can ban the ip address using common tools like iptables.
Timeline
- October 3, 2025, 11:26am EST: Issue reported to Cosmos Labs via an external team (via their Bug Bounty Program).
- October 3, 2025, 11:59am EST: Issue triaged by core team and core team completes validation of issue.
- October 6, 2025, 11:14pm EST: Issue reported to the Cosmos Bug Bounty Program (by original white hat reporter).
- October 9, 2025, 11:15am EST: Pre-notification delivered.
- October 10, 2025, 11:37am EST: Core team completes patch for the issue.
- October 14, 2025, 11:00am EST: Patch made available.
This issue was reported by @whoismxuse to the Cosmos Bug Bounty Program on HackerOne on October 6, 2025. If you believe you have found a bug in the Cosmos Stack or would like to contribute to the program by reporting a bug, please see https://hackerone.com/cosmos.
If there are questions about Cosmos security efforts, please reach out to our official communication channel at [[email protected]](mailto:[email protected]).
A Github Security Advisory for this issue is available in the CometBFT repository. For more information about CometBFT, see https://docs.cometbft.com/.
Credited to whoismxuse.
References
- https://github.com/cometbft/cometbft/security/advisories/GHSA-hrhf-2vcr-ghch
- https://github.com/cometbft/cometbft/commit/be5677c3e58f998b7f67bb6186dd2c9b81a041a1
- https://github.com/cometbft/cometbft/commit/dcb1f265b59477be40804f7ccdc4fb30612d6a4f
- https://github.com/cometbft/cometbft/releases/tag/v0.37.16
- https://github.com/cometbft/cometbft/releases/tag/v0.38.19
- https://github.com/advisories/GHSA-hrhf-2vcr-ghch
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-c32p-wcqj-j677
CometBFT has inconsistencies between how commit signatures are verified and how block time is derived
high7.1Jan 23, 2026CVE-2025-24371
CometBFT allows a malicious peer to make node stuck in blocksync
medium6.9Feb 3, 2025GHSA-r3r4-g7hq-pq4f
CometBFT allows a malicious peer to stall the network by disseminating seemingly valid block parts
highFeb 3, 2025GHSA-p7mv-53f2-4cwj
CometBFT Vote Extensions: Panic when receiving a Pre-commit with an invalid data
high8.3Nov 6, 2024GHSA-g5xx-c4hv-9ccc
CometBFT's state syncing validator from malicious node may lead to a chain split
low4.7Sep 3, 2024GHSA-hg58-rf2h-6rr7
CometBFT is unstability during blocksync when syncing from malicious peer
mediumJun 28, 2024
