How severe is GHSA-rj53-j6jw-7f7g?

No CVSS score has been assigned to GHSA-rj53-j6jw-7f7g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rj53-j6jw-7f7g?

GHSA-rj53-j6jw-7f7g affects the following packages: github.com/babylonlabs-io/babylon/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-rj53-j6jw-7f7g?

Update github.com/babylonlabs-io/babylon/v2 to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rj53-j6jw-7f7g is resolved across your whole dependency graph.

How do I detect GHSA-rj53-j6jw-7f7g 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-rj53-j6jw-7f7g if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-rj53-j6jw-7f7g actively exploited in the wild?

No public exploit code has been indexed for GHSA-rj53-j6jw-7f7g 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-rj53-j6jw-7f7g published, and has it been updated?

GHSA-rj53-j6jw-7f7g was published on July 8, 2025 and was last updated on July 28, 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

Babylon vulnerable to chain halt when a message modifies the validator set at the epoch boundaryGHSA-rj53-j6jw-7f7g

Fix: babylonlabs-io/babylon#1244

GHSA-rj53-j6jw-7f7g 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.

Also known asGO-2025-3801

Published

Jul 8, 2025

Updated

Jul 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

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

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 a message that modifies the validator set at the epoch boundary halts the chain.

Impact

Denial of Service - Comos-sdk prevents modifying the validator set from two different modules - https://github.com/cosmos/cosmos-sdk/blob/release/v0.50.x/types/module/module.go#L811. Such an operation leads to panic and chain halt.

Detailed Post mortem

https://boiling-lake-106.notion.site/2025-06-18-Genesis-mainnet-chain-halt-post-mortem-229f60cc1b5f80b7adf5e3ea0541ea87

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/babylonlabs-io/babylon/v2`	≥ 2.0.0&&< 2.1.0	2.1.0`go get github.com/babylonlabs-io/babylon/v2@v2.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/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.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rj53-j6jw-7f7g is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Summary Sending a message that modifies the validator set at the epoch boundary halts the chain. ### Impact Denial of Service - Comos-sdk prevents modifying the validator set from two different modules - https://github.com/cosmos/cosmos-sdk/blob/release/v0.50.x/types/module/module.go#L811. Such an operation leads to panic and chain halt. ### Detailed Post mortem https://boiling-lake-106.notion.site/2025-06-18-Genesis-mainnet-chain-halt-post-mortem-229f60cc1b5f80b7adf5e3ea0541ea87

O3 Security · Impact-Aware SCA

Is GHSA-rj53-j6jw-7f7g in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works