How severe is GHSA-869w-47c6-fq8q?

No CVSS score has been assigned to GHSA-869w-47c6-fq8q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-869w-47c6-fq8q?

GHSA-869w-47c6-fq8q affects the following packages: github.com/babylonlabs-io/babylon (Go). Ecosystems affected: Go.

How do I fix GHSA-869w-47c6-fq8q?

Update github.com/babylonlabs-io/babylon to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-869w-47c6-fq8q is resolved across your whole dependency graph.

How do I detect GHSA-869w-47c6-fq8q 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. 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-869w-47c6-fq8q 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-869w-47c6-fq8q?

O3 pinpoints whether GHSA-869w-47c6-fq8q 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-869w-47c6-fq8q actively exploited in the wild?

No public exploit code has been indexed for GHSA-869w-47c6-fq8q 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-869w-47c6-fq8q published, and has it been updated?

GHSA-869w-47c6-fq8q was published on May 15, 2025 and was last updated on May 22, 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-869w-47c6-fq8q

Babylon Integer Overflow in Distribution Module CumulativeRewardRatio Calculation Leading to Chain Halt

Also known asGO-2025-3687

Published

May 15, 2025

Updated

May 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹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

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/babylonlabs-io/babylon`	all versions	1.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. 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 to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-869w-47c6-fq8q 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-869w-47c6-fq8q 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-869w-47c6-fq8q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-869w-47c6-fq8q in your dependencies?

O3 detects GHSA-869w-47c6-fq8q 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