Is github.com/babylonlabs-io/babylon 0.13 vulnerable?
Go · 1 release from 0.13.0 to 0.13.0 · latest github.com/babylonlabs-io/babylon is 1.1.0 · checked 18 Nov 2026
Yes: 13 known advisories
Yes. github.com/babylonlabs-io/babylon 0.13.0, the last 0.13 release, is affected by 13 known security advisories (4 high, 1 medium, 8 low). At least one has no fixed release yet.
Is your project on an affected github.com/babylonlabs-io/babylon?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/babylonlabs-io/babylon 0.13.0
Babylon Nil BlockHash in BLS vote extensions triggers panics in consensus handlers in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon Incorrect FP inactive accounting in costaking creates “phantom stake” that earns rewards after BTC unbond in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon Incorrect FP inactive accounting in costaking creates “phantom stake” that earns rewards after BTC unbond
- Affected
- <=1.1.0
- Fixed in
- No fix released
Babylon Nil BlockHash in BLS vote extensions triggers panics in consensus handlers
- Affected
- <=1.1.0
- Fixed in
- No fix released
Babylon's malformed vote extensions are not rejected in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon's BIP322 signature implementation is not fully compliant to the spec in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon vulnerable to chain half when transaction has fees different than `ubbn` in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon vulnerable to chain halt when a message modifies the validator set at the epoch boundary in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon vulnerable to chain half when transaction has fees different than `ubbn`
- Affected
- <=1.1.0
- Fixed in
- No fix released
Babylon Finality Provider `MsgCommitPubRandList` replay attack in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon Integer Overflow in Distribution Module CumulativeRewardRatio Calculation Leading to Chain Halt in github.com/babylonlabs-io/babylon
- Affected
- All versions
- Fixed in
- No fix released
Babylon Integer Overflow in Distribution Module CumulativeRewardRatio Calculation Leading to Chain Halt
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Babylon Finality Provider `MsgCommitPubRandList` replay attack
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Which of your client projects are still on github.com/babylonlabs-io/babylon 0.13?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/babylonlabs-io/babylon version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/babylonlabs-io/babylon versions
- github.com/babylonlabs-io/babylon 0.16
- github.com/babylonlabs-io/babylon 0.15
- github.com/babylonlabs-io/babylon 0.14
- github.com/babylonlabs-io/babylon 0.12
- github.com/babylonlabs-io/babylon 0.11
- github.com/babylonlabs-io/babylon 0.10
- github.com/babylonlabs-io/babylon 1.1
- github.com/babylonlabs-io/babylon 1.0
- github.com/babylonlabs-io/babylon 0.18
- github.com/babylonlabs-io/babylon 0.17
- All github.com/babylonlabs-io/babylon advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.