CometBFT has inconsistencies between how commit signatures are verified and how block time is derived
Published 23 Jan 2026 · Updated 28 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 packages
- Affected
- >=0.38.0-alpha.1 <0.38.21
- Fixed in
- 0.38.21
go get github.com/cometbft/cometbft@v0.38.21- Affected
- <0.37.18
- Fixed in
- 0.37.18
go get github.com/cometbft/cometbft@v0.37.18Details
CSA-2026-001: Tachyon
Description
Name: CSA-2026-001: Tachyon
Criticality: Critical (Catastrophic Impact; Possible Likelihood per ACMv1.2)
Affected versions: All versions of CometBFT
Affected users: Validators and protocols relying on block timestamps
Description
A consensus-level vulnerability was discovered in CometBFT's "BFT Time" implementation due to an inconsistency between how commit signatures are verified and how block time is derived.
This breaks a core BFT Time guarantee: "A faulty process cannot arbitrarily increase the Time value."
Impact
Downstream impact on chains affects any module, smart contract, or system that relies on the block timestamp.
Patches
The new CometBFT releases v0.38.21 and v0.37.18 fix this issue. The main unreleased branch is also patched.
Workarounds
There are no effective workarounds for this vulnerability. Upgrading to patched versions is required.
Timeline
- January 8, 2026, 5:27PM UTC: Issue reported to Cosmos Bug Bounty Program
- January 9, 2026, 4:55AM UTC: Issue triaged and validated by core team
- January 12, 2026, 10:25PM UTC: Core team completes patch for the issue
- January 13, 2026 4:41PM UTC: Pre-notification delivered to ecosystem partners
- January 23, 2026, 3:00PM UTC: Patch made available
Credits
This issue was reported to the Cosmos Bug Bounty Program on HackerOne. Credit to SEAL 911 and QED Audit for the discovery and help with the patch.
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 you have questions about Cosmos security efforts, please reach out to our official communication channel at security@cosmoslabs.io.
A Github Security Advisory for this issue is available in the CometBFT repository. For more information about CometBFT, see https://docs.cometbft.com/.
Is GHSA-c32p-wcqj-j677 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
- Linkgithub.com/cometbft/cometbft/security/advisories/GHSA-c32p-wcqj-j677
- Linkgithub.com/cometbft/cometbft/commit/bf8274fcdbcab2bc652660ae627196a90a6efb97
- Packagegithub.com/cometbft/cometbft
- Linkgithub.com/cometbft/cometbft/releases/tag/v0.37.18
- Linkgithub.com/cometbft/cometbft/releases/tag/v0.38.21
- Linkpkg.go.dev/vuln/GO-2026-4361
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.