Babylon's BIP322 signature implementation is not fully compliant to the spec
Priority LOW 38CWE-347Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-347.
Summary
### 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.
Why it matters now
Fix Fixed github.com/babylonlabs-io/babylon/v4 (Go): 4.1.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/babylonlabs-io/babylon/v4 (Go) | before 4.1.0 | 4.1.0 | Patch available | GHSA-xq4h-wqm2-668w |
- github.com/babylonlabs-io/babylon/v4 (Go) Vendor— Affected before 4.1.0 Fixed in 4.1.0 Patch available GHSA-xq4h-wqm2-668w
Remediation
- Fix · GHSA-xq4h-wqm2-668w github.com/babylonlabs-io/babylon/v4 (Go) Fixed in 4.1.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-xq4h-wqm2-668w
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences