NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

GHSA-m6wq-66p2-c8pc: Babylon Nil BlockHash in BLS vote extensions triggers panics in consensus handlers

highCVSS 4.0 8.7

Summary A vulnerability exists in Babylon’s BLS vote extension processing where a malicious active validator can submit a VoteExtension with the blockhash field omitted from the protobuf serialization. Because protobuf fields are optional, unmarshalling succeeds but leaves BlockHash as nil.

Published Dec 8, 2025

Affected packages

github.com/babylonlabs-io/babylon/v4

Ecosystem
Go
Affected
< 4.2.0
Fixed in
4.2.0
Check
go list -m github.com/babylonlabs-io/babylon/v4

github.com/babylonlabs-io/babylon/v3

Ecosystem
Go
Affected
<= 3.0.0-snapshot.250805a
Fixed in
No patched version yet
Check
go list -m github.com/babylonlabs-io/babylon/v3

github.com/babylonlabs-io/babylon/v2

Ecosystem
Go
Affected
<= 2.3.2
Fixed in
No patched version yet
Check
go list -m github.com/babylonlabs-io/babylon/v2

github.com/babylonlabs-io/babylon

Ecosystem
Go
Affected
<= 1.1.0
Fixed in
No patched version yet
Check
go list -m github.com/babylonlabs-io/babylon

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

A vulnerability exists in Babylon’s BLS vote extension processing where a malicious active validator can submit a VoteExtension with the block_hash field omitted from the protobuf serialization. Because protobuf fields are optional, unmarshalling succeeds but leaves BlockHash as nil. Babylon then dereferences this nil pointer in consensus-critical code paths (notably VerifyVoteExtension, and also proposal-time vote verification), causing a runtime panic.

Impact

Intermittent validator crashes at epoch boundaries, which would slow down the creation of the epoch boundary block.

Finder

Vulnerability discovered by:

  • @GrumpyLaurie55348

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries