Babylon Nil BlockHash in BLS vote extensions triggers panics in consensus handlers

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?

Medium severity, with a CVSS score of 4, published 8 December 2025.

Which products and versions are affected?

github.com/babylonlabs-io/babylon (Go) SEMVER:introduced=0,last_affected=1.1.0; github.com/babylonlabs-io/babylon/v2 (Go) SEMVER:introduced=0,last_affected=2.3.2; github.com/babylonlabs-io/babylon/v3 (Go) SEMVER:introduced=0,last_affected=3.0.0-snapshot.250805a; github.com/babylonlabs-io/babylon/v4 (Go) SEMVER:introduced=0,fixed=4.2.0.

Is there a fix for This vulnerability?

Yes. github.com/babylonlabs-io/babylon/v4 (Go): upgrade to 4.2.0 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/babylonlabs-io/babylon (Go), github.com/babylonlabs-io/babylon/v2 (Go), github.com/babylonlabs-io/babylon/v3 (Go) or one of the others listed 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/babylonlabs-io/babylon/v4 (Go): upgrade to 4.2.0 or later

  go get github.com/babylonlabs-io/babylon/v4@v4.2.0

Affected products

• github.com/babylonlabs-io/babylon (Go) SEMVER:introduced=0,last_affected=1.1.0
• github.com/babylonlabs-io/babylon/v2 (Go) SEMVER:introduced=0,last_affected=2.3.2
• github.com/babylonlabs-io/babylon/v3 (Go) SEMVER:introduced=0,last_affected=3.0.0-snapshot.250805a
• github.com/babylonlabs-io/babylon/v4 (Go) SEMVER:introduced=0,fixed=4.2.0