Cosmos SDK: Groups module can halt chain when handling a malicious proposal

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: ASA-2025-003: Groups module can halt chain when handling a malicious proposal Component: CosmosSDK Criticality: High (Considerable Impact; Likely Likelihood per ACMv1.2) Affected versions: <= v0.47.15, <= 0.50.11 Affected users: Validators, Full nodes, Users on chains that utilize the groups module Description An issue was discovered in the groups module where a malicious proposal would result in a division by zero, and subsequently halt a chain due to the resulting error. Any user that can interact with the groups module can introduce this state. Patches The new Cosmos SDK release v0.50.12 and v0.47.16 fix this issue. Workarounds There are no known workarounds for this issue. It is advised that chains apply the update. Timeline February 9, 2025, 5:18pm PST: Issue reported to the Cosmos Bug Bounty program February 9, 2025, 8:12am PST: Issue triaged by Amulet on-call, and distributed to Core team February 9, 2025, 12:25pm PST: Core team completes validation of issue February 18,…

Published by the source

20 Feb 2025, 20:18 UTC

Last modified by the source

20 Feb 2025, 20:18 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x5vx-95h7-rv4p

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

# Patch Next advisory brief: GHSA-x5vx-95h7-rv4p

Advisory: Cosmos SDK: Groups module can halt chain when handling a malicious proposal
IDs: GHSA-x5vx-95h7-rv4p
Record: https://patchnext.com/advisories/ghsa-x5vx-95h7-rv4p (revision 1, source checked 26 Oct 2026, 15:08 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.12, 0.47.16-ics-lsm. A vendor fix does not mean a deployment is fixed.

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

## 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-x5vx-95h7-rv4p (GitHub-reviewed advisory GHSA-x5vx-95h7-rv4p lists affected ranges: Go github.com/cosmos/cosmos-sdk >=0 =0.50.0-alpha.0 <=0.50.11)

Commands are suggestions: review each one before running it.