How severe is GHSA-c32p-wcqj-j677?

No CVSS score has been assigned to GHSA-c32p-wcqj-j677 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c32p-wcqj-j677?

GHSA-c32p-wcqj-j677 affects the following packages: github.com/cometbft/cometbft (Go), github.com/cometbft/cometbft (Go). Ecosystems affected: Go.

How do I fix GHSA-c32p-wcqj-j677?

Update github.com/cometbft/cometbft to 0.38.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c32p-wcqj-j677 is resolved across your whole dependency graph.

How do I detect GHSA-c32p-wcqj-j677 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cometbft/cometbft, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c32p-wcqj-j677 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-c32p-wcqj-j677?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c32p-wcqj-j677 can be triaged on real exposure rather than presence alone.

Is GHSA-c32p-wcqj-j677 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c32p-wcqj-j677 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-c32p-wcqj-j677 published, and has it been updated?

GHSA-c32p-wcqj-j677 was published on January 23, 2026 and was last updated on February 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-c32p-wcqj-j677 — cometbft

Fix: cometbft/cometbft@bf8274f

GHSA-c32p-wcqj-j677 is a security vulnerability in github.com/cometbft/cometbft. A fix is available for github.com/cometbft/cometbft — see the affected versions and patch details below.

CometBFT has inconsistencies between how commit signatures are verified and how block time is derived

Also known asGO-2026-4361

Published

Jan 23, 2026

Updated

Feb 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Feb 28, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/cometbft/cometbft🐹github.com/cometbft/cometbft

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cometbft/cometbft`	≥ 0.38.0-alpha.1&&< 0.38.21	0.38.21`go get github.com/cometbft/cometbft@v0.38.21`
🐹Go	`github.com/cometbft/cometbft`	all versions	0.37.18`go get github.com/cometbft/cometbft@v0.37.18`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cometbft/cometbft, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cometbft/cometbft to 0.38.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c32p-wcqj-j677 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c32p-wcqj-j677 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-c32p-wcqj-j677. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# 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 gu

O3 Security · Impact-Aware SCA

Is GHSA-c32p-wcqj-j677 in your dependencies?

O3 Security finds GHSA-c32p-wcqj-j677 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-c32p-wcqj-j677 — cometbft

Real-World Exposure

Description

CSA-2026-001: Tachyon

Description

Description

Impact

Patches

Workarounds

Timeline

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-c32p-wcqj-j677 in your dependencies?