Summary
Babylon Integer Overflow in Distribution Module CumulativeRewardRatio Calculation Leading to Chain Halt
Minting large amount of tokens through ibc transfer and then depositing them in validator rewards pool (via DepositValidatorRewardsPool message) can lead to integer overflow panic when calculating cumulative_reward_ratio for the validator.
This calculation happens in x/epoching module EndBlocker, thus the panic will halt the chain.
Impact
Denial of Service - Due to panic in the EndBlocker Babylon Genesis will halt
An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.
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-869W-47C6-FQ8Q? GHSA-869W-47C6-FQ8Q is a high-severity integer overflow or wraparound vulnerability in github.com/babylonlabs-io/babylon (go), affecting versions < 1.1.0. It is fixed in 1.1.0. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
- Which versions of github.com/babylonlabs-io/babylon are affected by GHSA-869W-47C6-FQ8Q? github.com/babylonlabs-io/babylon (go) versions < 1.1.0 is affected.
- Is there a fix for GHSA-869W-47C6-FQ8Q? Yes. GHSA-869W-47C6-FQ8Q is fixed in 1.1.0. Upgrade to this version or later.
- Is GHSA-869W-47C6-FQ8Q exploitable, and should I be worried? Whether GHSA-869W-47C6-FQ8Q 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-869W-47C6-FQ8Q 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-869W-47C6-FQ8Q? Upgrade
github.com/babylonlabs-io/babylonto 1.1.0 or later.