# GO-2026-4361 - Inconsistencies between how commit signatures are verified and how block time is derived in…

Source: https://junglewise.ai/threats/go-2026-4361-inconsistencies-between-how-commit-signatures-are-verified-92e2eeac  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-19  
License: CC BY 4.0 with a link back

Severity: info · Published 2026-02-19

Inconsistencies between how commit signatures are verified and how block time is derived in github.com/cometbft/cometbft

Technologies: [github.com/cometbft/cometbft (Go)](https://junglewise.ai/threats/technologies/github-com-cometbft-cometbft). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Informational severity, published 19 February 2026.

**Which products and versions are affected?** github.com/cometbft/cometbft (Go) SEMVER:introduced=0,fixed=0.37.18,introduced=0.38.0-alpha.1,fixed=0.38.21.

**Is there a fix for This vulnerability?** Yes. github.com/cometbft/cometbft (Go): upgrade to 0.38.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected?** Check whether you run github.com/cometbft/cometbft (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/cometbft/cometbft (Go): upgrade to 0.38.21 or later

  ```sh
  go get github.com/cometbft/cometbft@v0.38.21
  ```


## Affected products

- github.com/cometbft/cometbft (Go) SEMVER:introduced=0,fixed=0.37.18,introduced=0.38.0-alpha.1,fixed=0.38.21

## Related threats

- [CometBFT has inconsistencies between how commit signatures are verified and how block time is derived](https://junglewise.ai/threats/cometbft-has-inconsistencies-between-how-commit-signatures-are-verified-17e99f94)
- [GO-2025-4025 - CometBFT's invalid BitArray handling can lead to network halt in github.com/cometbft/cometbft](https://junglewise.ai/threats/go-2025-4025-cometbft-s-invalid-bitarray-handling-can-lead-to-network-6ea1281e)
- [CometBFT's invalid BitArray handling can lead to network halt](https://junglewise.ai/threats/cometbft-s-invalid-bitarray-handling-can-lead-to-network-halt-df96de9f)
- [GO-2025-3443 - CometBFT allows a malicious peer to stall network by disseminating valid-looking block parts in…](https://junglewise.ai/threats/go-2025-3443-cometbft-allows-a-malicious-peer-to-stall-network-by-84bcffee)
- [GO-2025-3442 - CometBFT allows a malicious peer to make node stuck in blocksync in github.com/cometbft/cometbft](https://junglewise.ai/threats/cve-2025-24371-cometbft-allows-a-malicious-peer-to-make-node-stuck-in-blocksync)