Summary
Babylon vulnerable to chain halt when a message modifies the validator set at the epoch boundary
Sending a message that modifies the validator set at the epoch boundary halts the chain.
Detailed Post mortem
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-RJ53-J6JW-7F7G? GHSA-RJ53-J6JW-7F7G is a high-severity security vulnerability in github.com/babylonlabs-io/babylon/v2 (go), affecting versions >= 2.0.0, < 2.1.0. It is fixed in 2.1.0.
- Which versions of github.com/babylonlabs-io/babylon/v2 are affected by GHSA-RJ53-J6JW-7F7G? github.com/babylonlabs-io/babylon/v2 (go) versions >= 2.0.0, < 2.1.0 is affected.
- Is there a fix for GHSA-RJ53-J6JW-7F7G? Yes. GHSA-RJ53-J6JW-7F7G is fixed in 2.1.0. Upgrade to this version or later.
- Is GHSA-RJ53-J6JW-7F7G exploitable, and should I be worried? Whether GHSA-RJ53-J6JW-7F7G is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-RJ53-J6JW-7F7G is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-RJ53-J6JW-7F7G? Upgrade
github.com/babylonlabs-io/babylon/v2to 2.1.0 or later.