LowGO-2026-4361GHSA-c32p-wcqj-j677
Inconsistencies between how commit signatures are verified and how block time is derived in github.com/cometbft/cometbft
Published 19 Feb 2026 · Updated 25 Feb 2026
Is your project on an affected github.com/cometbft/cometbft?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.37.18 · >=0.38.0-alpha.1 <0.38.21
- Fixed in
- 0.37.18, 0.38.21
Update to the fixed version for your release line, for example:
go get github.com/cometbft/cometbft@v0.38.21Details
Inconsistencies between how commit signatures are verified and how block time is derived in github.com/cometbft/cometbft
Is GO-2026-4361 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-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
- HighGHSA-r3r4-g7hq-pq4fCometBFT allows a malicious peer to stall the network by disseminating seemingly valid block parts · 3 Feb 2025
- MediumCVE-2025-24371CometBFT allows a malicious peer to make node stuck in blocksync · 3 Feb 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.