How severe is GHSA-m6wq-66p2-c8pc?

No CVSS score has been assigned to GHSA-m6wq-66p2-c8pc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m6wq-66p2-c8pc?

GHSA-m6wq-66p2-c8pc affects the following packages: github.com/babylonlabs-io/babylon/v4 (Go), github.com/babylonlabs-io/babylon/v3 (Go), github.com/babylonlabs-io/babylon/v2 (Go), github.com/babylonlabs-io/babylon (Go). Ecosystems affected: Go.

How do I fix GHSA-m6wq-66p2-c8pc?

Update github.com/babylonlabs-io/babylon/v4 to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6wq-66p2-c8pc is resolved across your whole dependency graph.

How do I detect GHSA-m6wq-66p2-c8pc in my Go dependencies?

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

How do I mitigate GHSA-m6wq-66p2-c8pc 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-m6wq-66p2-c8pc?

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

Is GHSA-m6wq-66p2-c8pc actively exploited in the wild?

No public exploit code has been indexed for GHSA-m6wq-66p2-c8pc 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-m6wq-66p2-c8pc published, and has it been updated?

GHSA-m6wq-66p2-c8pc was published on December 8, 2025 and was last updated on December 17, 2025. 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-m6wq-66p2-c8pc — v4

Fix: babylonlabs-io/babylon@f79ad58

GHSA-m6wq-66p2-c8pc is a security vulnerability in github.com/babylonlabs-io/babylon/v4. A fix is available for github.com/babylonlabs-io/babylon/v4 — see the affected versions and patch details below.

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

Also known asGO-2025-4211

Published

Dec 8, 2025

Updated

Dec 17, 2025

Affected

4 pkgs

Patched

1 / 4

Exploits

None indexed

Exploitation data as of Dec 17, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

🐹github.com/babylonlabs-io/babylon/v4🐹github.com/babylonlabs-io/babylon/v3🐹github.com/babylonlabs-io/babylon/v2🐹github.com/babylonlabs-io/babylon

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

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

Affected Packages

4 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/babylonlabs-io/babylon/v4`	all versions	4.2.0`go get github.com/babylonlabs-io/babylon/v4@v4.2.0`
🐹Go	`github.com/babylonlabs-io/babylon/v3`	all versions	No fix
🐹Go	`github.com/babylonlabs-io/babylon/v2`	all versions	No fix
🐹Go	`github.com/babylonlabs-io/babylon`	all versions	No fix

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/babylonlabs-io/babylon/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/babylonlabs-io/babylon/v4 to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6wq-66p2-c8pc 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-m6wq-66p2-c8pc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m6wq-66p2-c8pc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-m6wq-66p2-c8pc in your dependencies?

O3 Security finds GHSA-m6wq-66p2-c8pc 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