Babylon's BIP322 signature implementation is not fully compliant to the spec

published 2025-11-24 11mo ago modified 2026-03-03 8mo ago also GO-2025-4159

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### Summary

The BIP-322 signature verification does not enforce the SIGHASH value to be SIGHASH_ALL, and therefore is not strictly following the [spec](https://bips.dev/322/).

### Impact

Non-compliant BIP-322 signatures in proof of possessions can be accepted by the chain.

Patch / fix

fixed in 1 links 1

go github.com/babylonlabs-io/babylon/v4 4.1.0

github.com/babylonlabs-io/babylon@6e8bdd3 commit

Is GHSA-xq4h-wqm2-668w in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
go	github.com/babylonlabs-io/babylon/v4	<4.1.0	4.1.0
go	github.com/babylonlabs-io/babylon	all versions	no fix listed
go	github.com/babylonlabs-io/babylon/v2	all versions	no fix listed
go	github.com/babylonlabs-io/babylon/v3	all versions	no fix listed

Classification

Weakness

CWE-347 Improper Verification of Cryptographic Signature

References

github.com /babylonlabs-io/babylon/commit/6e8bdd328a47343fcd7ad98d1b0c7267860b019a
web, patch
github.com /babylonlabs-io/babylon/security/advisories/GHSA-xq4h-wqm2-668w
web, advisory
bips.dev /322
web
github.com /babylonlabs-io/babylon
package

Sources

GitHub Advisory GHSA-xq4h-wqm2-668w
OSV GO-2025-4159

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.