NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

GHSA-c32p-wcqj-j677: CometBFT has inconsistencies between how commit signatures are verified and how block time is derived

highCVSS 4.0 7.1

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…

Published Jan 23, 2026 · Updated Feb 27, 2026

Affected packages

github.com/cometbft/cometbft

Ecosystem
Go
Affected
>= 0.38.0-alpha.1, <= 0.38.20
Fixed in
0.38.21
Check
go list -m github.com/cometbft/cometbft

github.com/cometbft/cometbft

Ecosystem
Go
Affected
<= 0.37.17
Fixed in
0.37.18
Check
go list -m github.com/cometbft/cometbft

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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/.

References

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 entries