GHSA-xq4h-wqm2-668w: Babylon's BIP322 signature implementation is not fully compliant to the spec
Summary The BIP-322 signature verification does not enforce the SIGHASH value to be SIGHASHALL, and therefore is not strictly following the spec. Impact Non-compliant BIP-322 signatures in proof of possessions can be accepted by the chain.
Published Nov 24, 2025
Affected packages
github.com/babylonlabs-io/babylon/v4
- Ecosystem
- Go
- Affected
- < 4.1.0
- Fixed in
- 4.1.0
- Check
go list -m github.com/babylonlabs-io/babylon/v4
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The BIP-322 signature verification does not enforce the SIGHASH value to be SIGHASH_ALL, and therefore is not strictly following the spec.
Impact
Non-compliant BIP-322 signatures in proof of possessions can be accepted by the chain.
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 entriesGHSA-4rmq-mc2c-r495
Babylon Incorrect FP inactive accounting in costaking creates “phantom stake” that earns rewards after BTC unbond
medium6.9No fixDec 9, 2025GHSA-m6wq-66p2-c8pc
Babylon Nil BlockHash in BLS vote extensions triggers panics in consensus handlers
high8.7No fixDec 8, 2025GHSA-2fcv-qww3-9v6h
Babylon's malformed vote extensions are not rejected
high7.0Nov 24, 2025
