go package report

Is github.com/babylonlabs-io/babylon/v3 safe?

2 known vulnerabilities, worst severity HIGH.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so go packages are not covered.


      cvss
      0.0
      high

      severity band, no base score published

      epss
      not scored

      chance of exploitation in 30 days

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — GHSA-m6wq-66p2-c8pc, the advisory selected below

      // 2 advisories

      GHSA-m6wq-66p2-c8pc

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

      Checked 2026-09-27 at 21:37 UTC. The most recent advisory here was published 2025-12-09. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.