Cosmos SDK: x/group can halt when erroring in EndBlocker

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.50 testnet with the failing state and did not halt…

Published by the source

12 Mar 2025, 19:28 UTC

Last modified by the source

20 Aug 2025, 17:39 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-47ww-ff84-4jrg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-47ww-ff84-4jrg

Advisory: Cosmos SDK: x/group can halt when erroring in EndBlocker
IDs: GHSA-47ww-ff84-4jrg
Record: https://patchnext.com/advisories/ghsa-47ww-ff84-4jrg (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cosmos/cosmos-sdk 0.50.13, 0.47.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cosmos/cosmos-sdk: affected >= 0.50.0-alpha.0, <= 0.50.12; <= 0.47.16; fixed in 0.47.17, 0.50.13

## Suggested inspection (read-only)
- Go github.com/cosmos/cosmos-sdk: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cosmos/cosmos-sdk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-47ww-ff84-4jrg (GitHub-reviewed advisory GHSA-47ww-ff84-4jrg lists affected ranges: Go github.com/cosmos/cosmos-sdk >=0.50.0-alpha.0 =0 <=0.47.16)

Commands are suggestions: review each one before running it.