GitHub Advisoryadvisory · Go

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

HIGH Published 2026-01-23 Modified 2026-02-27 Official page ↗
Ecosystem
Go
Packages
github.com/cometbft/cometbft
Severity
High
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-703
Reviewed
2026-01-23

Affected packages

• Go github.com/cometbft/cometbft: >= 0.38.0-alpha.1, < 0.38.21 → fixed in 0.38.21 • Go github.com/cometbft/cometbft: < 0.37.18 → fixed in 0.37.18

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

Related

Weakness · CWE (1)

  • CWE-703 Improper Check or Handling of Exceptional Conditions weakness

References