GHSA-c32p-wcqj-j677: CometBFT has inconsistencies between how commit signatures are verified and how block time is derived
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/cometbft/cometbft (Go) 0.38.21, 0.37.18.
Low priority for now. Upgrade to github.com/cometbft/cometbft (Go) 0.38.21, 0.37.18 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
# CSA-2026-001: Tachyon ## Description **Name:** CSA-2026-001: Tachyon **Criticality:** Critical (Catastrophic Impact; Possible Likelihood per [ACMv1.2](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md)) **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](https://github.com/cometbft/cometbft/releases/tag/v0.38.21) and [v0.37.18](https://github.com/cometbft/cometbft/releases/tag/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](https://x.com/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/.
- Published
- Jan 23, 2026
- Updated
- Feb 28, 2026
- EPSS
- —
- CWE
- CWE-703
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/cometbft/cometbft | pkg:golang/github.com/cometbft/cometbft |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/cometbft/cometbft | from 0.38.0-alpha.1 · before 0.38.21 | 0.38.21 |
| Go | github.com/cometbft/cometbft | before 0.37.18 | 0.37.18 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GO-2026-4361Inconsistencies between how commit signatures are verified and how block time is derived in github.com/cometbft/cometbft0Monitor
- GO-2025-4025CometBFT's invalid BitArray handling can lead to network halt in github.com/cometbft/cometbft0Monitor
- GHSA-hrhf-2vcr-ghchCometBFT's invalid BitArray handling can lead to network halt0Monitor
Published before and after this one in the same product
- ← EarlierGO-2024-3259Nov 20, 2024 · CometBFT Vote Extensions: Panic when receiving a Pre-commit with an invalid data in github.com/cometbft/cometbft0Monitor
- ← EarlierGHSA-r3r4-g7hq-pq4fFeb 3, 2025 · CometBFT allows a malicious peer to stall the network by disseminating seemingly valid block parts0Monitor
- ← EarlierGO-2025-3443Feb 4, 2025 · CometBFT allows a malicious peer to stall network by disseminating valid-looking block parts in github.com/cometbft/cometbft0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/cometbft/cometbft | 0.37.18 | Package registry (OSV) |
| Go:github.com/cometbft/cometbft | 0.38.21 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
Weakness class (CWE)
CWE-703 · Improper Check or Handling of Exceptional ConditionsCVSS 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
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Fix✗ → ✓
- CVSS8 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.