Skip to main content
VulnerabilityPublished Updated

github.com/babylonlabs-io/babylon/v4 · V4: Babylon's BIP322 signature implementation is not fully compliant to the spec

Affects github.com/babylonlabs-io/babylon/v4Source GCVE Database

0

CVSS 6.9 Medium : upgrade to 4.1.0 when convenient.

Data as of 19 Nov 2026, 02:51 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

What to do

Upgrade github.com/babylonlabs-io/babylon/v4 to 4.1.0.

Affected software

ProductAffectedFixed in
Gogithub.com/babylonlabs-io/babylon/v4Affected
  • <4.1.0
Fixed in
  • 4.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Babylon to version 4.1.0 or later, where the BIP-322 signature verification enforces the SIGHASH_ALL requirement and complies with the specification. Since a patch is available, applying this official fix is the recommended remediation.

Description

Babylon's implementation of BIP-322 signature verification does not enforce the SIGHASH value to be SIGHASH_ALL, which deviates from the official specification. This non-compliance allows non-standard BIP-322 signatures in proof of possession to be accepted by the chain. The vulnerability affects versions prior to 4.1.0 and has a medium severity rating with a CVSS score of 6.9. A fix is available in version 4.1.0.

References

Community reviews

Loading reviews…