Skip to content
Fencer Intel
high —

GHSA-rj53-j6jw-7f7g json

Babylon vulnerable to chain halt when a message modifies the validator set at the epoch boundary

published last yr. modified 8mo ago also GO-2025-3801

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/babylonlabs-io/babylon/v2 2.1.0

Is GHSA-rj53-j6jw-7f7g in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/babylonlabs-io/babylon/v2
>=2.0.0, <2.1.0
2.1.0
go github.com/babylonlabs-io/babylon
all versions
 no fix listed

Classification

Weakness
  • CWE-754 Improper Check for Unusual or Exceptional Conditions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.