How severe is GHSA-47ww-ff84-4jrg?

No CVSS score has been assigned to GHSA-47ww-ff84-4jrg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-47ww-ff84-4jrg?

GHSA-47ww-ff84-4jrg affects the following packages: github.com/cosmos/cosmos-sdk (Go), github.com/cosmos/cosmos-sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-47ww-ff84-4jrg?

Update github.com/cosmos/cosmos-sdk to 0.50.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47ww-ff84-4jrg is resolved across your whole dependency graph.

How do I detect GHSA-47ww-ff84-4jrg 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-47ww-ff84-4jrg 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-47ww-ff84-4jrg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-47ww-ff84-4jrg can be triaged on real exposure rather than presence alone.

Is GHSA-47ww-ff84-4jrg actively exploited in the wild?

No public exploit code has been indexed for GHSA-47ww-ff84-4jrg 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-47ww-ff84-4jrg published, and has it been updated?

GHSA-47ww-ff84-4jrg was published on March 12, 2025 and was last updated on August 20, 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-47ww-ff84-4jrg — cosmos-sdk

Fix: cosmos/cosmos-sdk@cbd69fb

GHSA-47ww-ff84-4jrg 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: x/group can halt when erroring in EndBlocker

Also known asGO-2025-3516

Published

Mar 12, 2025

Updated

Aug 20, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 20, 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: 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 (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]. 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.50.0-alpha.0&&< 0.50.13	0.50.13`go get github.com/cosmos/cosmos-sdk@v0.50.13`
🐹Go	`github.com/cosmos/cosmos-sdk`	all versions	0.47.17`go get github.com/cosmos/cosmos-sdk@v0.47.17`

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.50.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47ww-ff84-4jrg 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-47ww-ff84-4jrg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-47ww-ff84-4jrg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Name: ISA-2025-002: x/group can halt when erroring in EndBlocker 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.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

O3 Security · Impact-Aware SCA

Is GHSA-47ww-ff84-4jrg in your dependencies?

O3 Security finds GHSA-47ww-ff84-4jrg 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-47ww-ff84-4jrg — cosmos-sdk

Real-World Exposure

Description

Description

Patches

Testing

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-47ww-ff84-4jrg in your dependencies?