How severe is GHSA-56j4-446m-qrf6?

No CVSS score has been assigned to GHSA-56j4-446m-qrf6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-56j4-446m-qrf6?

GHSA-56j4-446m-qrf6 affects the following packages: github.com/babylonlabs-io/babylon/v2 (Go), github.com/babylonlabs-io/babylon (Go). Ecosystems affected: Go.

How do I fix GHSA-56j4-446m-qrf6?

Update github.com/babylonlabs-io/babylon/v2 to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56j4-446m-qrf6 is resolved across your whole dependency graph.

How do I detect GHSA-56j4-446m-qrf6 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/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-56j4-446m-qrf6 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-56j4-446m-qrf6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-56j4-446m-qrf6 can be triaged on real exposure rather than presence alone.

Is GHSA-56j4-446m-qrf6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-56j4-446m-qrf6 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-56j4-446m-qrf6 published, and has it been updated?

GHSA-56j4-446m-qrf6 was published on June 30, 2025 and was last updated on July 29, 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

Not in CISA KEV

GHSA-56j4-446m-qrf6 — v2

Fix: babylonlabs-io/babylon@fe67aeb

GHSA-56j4-446m-qrf6 is a security vulnerability in github.com/babylonlabs-io/babylon/v2. A fix is available for github.com/babylonlabs-io/babylon/v2 — see the affected versions and patch details below.

Babylon vulnerable to chain half when transaction has fees different than `ubbn`

Also known asGO-2025-3791

Published

Jun 30, 2025

Updated

Jul 29, 2025

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Jul 29, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

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

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

Sending transactions with fees different than native Babylon genesis denom (ubbn) leads to chain halt.

Impact

Denial of Service - Due to panic in the x/distribution module BeginBlocker triggered by a error when sending fees from feeCollector to x/distribution module - https://github.com/cosmos/cosmos-sdk/blob/main/x/distribution/keeper/allocation.go#L28 Babylon Genesis will halt

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/babylonlabs-io/babylon/v2`	all versions	2.2.0`go get github.com/babylonlabs-io/babylon/v2@v2.2.0`
🐹Go	`github.com/babylonlabs-io/babylon`	all versions	No fix

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/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/babylonlabs-io/babylon/v2 to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56j4-446m-qrf6 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-56j4-446m-qrf6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-56j4-446m-qrf6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Sending transactions with fees different than native Babylon genesis denom (`ubbn`) leads to chain halt. ### Impact Denial of Service - Due to panic in the `x/distribution` module `BeginBlocker` triggered by a error when sending fees from `feeCollector` to `x/distribution` module - https://github.com/cosmos/cosmos-sdk/blob/main/x/distribution/keeper/allocation.go#L28 Babylon Genesis will halt

O3 Security · Impact-Aware SCA

Is GHSA-56j4-446m-qrf6 in your dependencies?

O3 Security finds GHSA-56j4-446m-qrf6 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works