How severe is GHSA-x5vx-95h7-rv4p?

No CVSS score has been assigned to GHSA-x5vx-95h7-rv4p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x5vx-95h7-rv4p?

GHSA-x5vx-95h7-rv4p affects the following packages: github.com/cosmos/cosmos-sdk (Go), github.com/cosmos/cosmos-sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-x5vx-95h7-rv4p?

Update github.com/cosmos/cosmos-sdk to 0.47.16-ics-lsm or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5vx-95h7-rv4p is resolved across your whole dependency graph.

How do I detect GHSA-x5vx-95h7-rv4p in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cosmos/cosmos-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x5vx-95h7-rv4p 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-x5vx-95h7-rv4p?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-x5vx-95h7-rv4p can be triaged on real exposure rather than presence alone.

Is GHSA-x5vx-95h7-rv4p actively exploited in the wild?

No public exploit code has been indexed for GHSA-x5vx-95h7-rv4p 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-x5vx-95h7-rv4p published, and has it been updated?

GHSA-x5vx-95h7-rv4p was published on February 20, 2025 and was last updated on March 3, 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

Not in CISA KEV

GHSA-x5vx-95h7-rv4p — cosmos-sdk

Fix: cosmos/cosmos-sdk@0a98b65

GHSA-x5vx-95h7-rv4p is a security vulnerability in github.com/cosmos/cosmos-sdk. A fix is available for github.com/cosmos/cosmos-sdk — see the affected versions and patch details below.

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

Also known asGO-2025-3476

Published

Feb 20, 2025

Updated

Mar 3, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Mar 3, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐹github.com/cosmos/cosmos-sdk🐹github.com/cosmos/cosmos-sdk

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

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, 2025, 8:00am PST / 17:00 CET: Pre-notification delivered
February 20, 2025, 8:00am PST / 17:00 CET: Patch made available

This issue was reported to the Cosmos Bug Bounty Program by dongsam on HackerOne on February 9, 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]. 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.

A Github Security Advisory for this issue is available in the Cosmos SDK repository.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/cosmos-sdk`	all versions	0.47.16-ics-lsm`go get github.com/cosmos/cosmos-sdk@v0.47.16-ics-lsm`
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.50.0-alpha.0&&< 0.50.12	0.50.12`go get github.com/cosmos/cosmos-sdk@v0.50.12`

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/cosmos/cosmos-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cosmos/cosmos-sdk to 0.47.16-ics-lsm or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5vx-95h7-rv4p 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-x5vx-95h7-rv4p can be triaged on real exposure rather than presence alone.

Tailored to GHSA-x5vx-95h7-rv4p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md)) 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 int

O3 Security · Impact-Aware SCA

Is GHSA-x5vx-95h7-rv4p in your dependencies?

O3 Security finds GHSA-x5vx-95h7-rv4p across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-x5vx-95h7-rv4p — cosmos-sdk

Real-World Exposure

Description

Description

Patches

Workarounds

Timeline

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-x5vx-95h7-rv4p in your dependencies?