GHSA-c32p-wcqj-j677 CometBFT has inconsistencies between how commit signatures are verified and how block time is derived
Attackers can manipulate block timestamps by exploiting signature verification inconsistencies, affecting blockchain consensus integrity.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-c32p-wcqj-j677?
GHSA-c32p-wcqj-j677 is a vulnerability in github.com/cometbft/cometbft, published on 23 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
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 [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/.
Which versions are affected by GHSA-c32p-wcqj-j677?
5 open source packages ship an affected version, including github.com/cometbft/cometbft.
| Package | Affected | Fixed in |
|---|---|---|
github.com/cometbft/cometbft Go | All versions | 0.37.18, 0.38.21 |
github.com/cometbft/cometbft Go | All versions | 0.37.18 |
github.com/cometbft/cometbft Go | All versions | 0.37.18 |
github.com/cometbft/cometbft Go | From 0.38.0-alpha.1 | 0.38.21 |
github.com/cometbft/cometbft Go | From 0.38.0-alpha.1 | 0.38.21 |
How do I fix GHSA-c32p-wcqj-j677?
Upgrade github.com/cometbft/cometbft to a fixed version for your release line: 0.37.18 or 0.38.21.
Is GHSA-c32p-wcqj-j677 being exploited?
There is no known exploitation of GHSA-c32p-wcqj-j677 in the wild and no public exploit code.
Sources
Also known as GO-2026-4361.