GHSA-47ww-ff84-4jrg: Cosmos SDK: x/group can halt when erroring in EndBlocker
Name: ISA-2025-002: x/group can halt when erroring in EndBlocker Component: CosmosSDK Criticality: High (Considerable Impact; Likely Likelihood per ACMv1.2) Affected versions: <= v0.47.16, <= 0.50.12 Affected users: Validators, Full nodes, Users on chains that utilize the groups module Cosmos SDK chains in unpatched releases that use the x/group module are affected.
Published Mar 12, 2025 · Updated Aug 20, 2025
Affected packages
github.com/cosmos/cosmos-sdk
- Ecosystem
- Go
- Affected
- >= 0.50.0-alpha.0, <= 0.50.12
- Fixed in
- 0.50.13
- Check
go list -m github.com/cosmos/cosmos-sdk
github.com/cosmos/cosmos-sdk
- Ecosystem
- Go
- Affected
- <= 0.47.16
- Fixed in
- 0.47.17
- Check
go list -m github.com/cosmos/cosmos-sdk
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Name: ISA-2025-002: x/group can halt when erroring in EndBlocker Component: CosmosSDK Criticality: High (Considerable Impact; Likely Likelihood per ACMv1.2) Affected versions: <= v0.47.16, <= 0.50.12 Affected users: Validators, Full nodes, Users on chains that utilize the groups module Cosmos SDK chains in unpatched releases that use the x/group module are affected.
Description
An issue was discovered in the groups module where malicious proposals would result in an errors triggered in the module's end blocker that could result in a chain halt. Any set of users that can interact with the groups module could introduce this state.
Patches
_Has the problem been patched? What versions should users upgrade to?_
The new Cosmos SDK release v0.50.13 and v0.47.17 fix this issue.
Testing
Testing we have done to gain more confidence in this release:
In addition to testing Cosmos SDK we also did the following:
- Ran a patched node in a local
v0.50testnet with the failing state and did not halt (an unpatched network confirmed to halt) - Ran a patched node on Xion Mainnet (uses
x/group) - Ran a patched node on Zetachain Mainnet (uses
x/xgroup)
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
There are no known workarounds for this issue. It is advised that chains apply the update.
This issue was reported to the Cosmos Bug Bounty Program by wbowling on HackerOne on February 28, 2025. If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see https://hackerone.com/cosmos.
If you have questions about Interchain security efforts, please reach out to our official communication channel at [[email protected]](mailto:[email protected]). For more information about the Interchain Foundation’s engagement with Amulet, and to sign up for security notification emails, please see https://github.com/interchainio/security.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-p22h-3m2v-cmgh
Cosmos SDK's Integer Overflow vulnerability in its Validator Rewards pool can cause a chain halt
high7.7Jul 8, 2025GHSA-x5vx-95h7-rv4p
Cosmos SDK: Groups module can halt chain when handling a malicious proposal
high8.7Feb 20, 2025GHSA-8wcc-m6j2-qxvm
ASA-2024-0012, ASA-2024-0013: CosmosSDK: Transaction decoding may result in a stack overflow or resource exhaustion
high8.7Dec 16, 2024GHSA-95rx-m9m5-m94v
ASA-2024-006: ValidateVoteExtensions helper function in Cosmos SDK may allow incorrect voting power assumptions
high7.1Mar 12, 2024GHSA-86h5-xcpx-cfqc
ASA-2024-005: Potential slashing evasion during re-delegation
lowFeb 27, 2024GHSA-2557-x9mg-76w8
ASA-2024-002: Default `PrepareProposalHandler` may produce invalid proposals when used with default `SenderNonceMempool`
medium5.3Feb 21, 2024
