How severe is GHSA-xq4h-wqm2-668w?

No CVSS score has been assigned to GHSA-xq4h-wqm2-668w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xq4h-wqm2-668w?

GHSA-xq4h-wqm2-668w affects the following packages: github.com/babylonlabs-io/babylon/v4 (Go). Ecosystems affected: Go.

How do I fix GHSA-xq4h-wqm2-668w?

Update github.com/babylonlabs-io/babylon/v4 to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq4h-wqm2-668w is resolved across your whole dependency graph.

How do I detect GHSA-xq4h-wqm2-668w in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/babylonlabs-io/babylon/v4. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xq4h-wqm2-668w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-xq4h-wqm2-668w?

O3 pinpoints whether GHSA-xq4h-wqm2-668w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xq4h-wqm2-668w actively exploited in the wild?

No public exploit code has been indexed for GHSA-xq4h-wqm2-668w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xq4h-wqm2-668w published, and has it been updated?

GHSA-xq4h-wqm2-668w was published on November 24, 2025 and was last updated on November 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-xq4h-wqm2-668w

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

Also known asGO-2025-4159

Published

Nov 24, 2025

Updated

Nov 27, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/babylonlabs-io/babylon/v4

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/babylonlabs-io/babylon/v4`	all versions	4.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/babylonlabs-io/babylon/v4. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/babylonlabs-io/babylon/v4 to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq4h-wqm2-668w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xq4h-wqm2-668w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xq4h-wqm2-668w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-xq4h-wqm2-668w in your dependencies?

O3 detects GHSA-xq4h-wqm2-668w across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works