How severe is GHSA-86h5-xcpx-cfqc?

No CVSS score has been assigned to GHSA-86h5-xcpx-cfqc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-86h5-xcpx-cfqc?

GHSA-86h5-xcpx-cfqc affects the following packages: github.com/cosmos/cosmos-sdk (Go), github.com/cosmos/cosmos-sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-86h5-xcpx-cfqc?

Update github.com/cosmos/cosmos-sdk to 0.50.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86h5-xcpx-cfqc is resolved across your whole dependency graph.

How do I detect GHSA-86h5-xcpx-cfqc 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-86h5-xcpx-cfqc 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.

Is GHSA-86h5-xcpx-cfqc actively exploited in the wild?

No public exploit code has been indexed for GHSA-86h5-xcpx-cfqc 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-86h5-xcpx-cfqc published, and has it been updated?

GHSA-86h5-xcpx-cfqc was published on February 27, 2024 and was last updated on November 4, 2024. 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

ASA-2024-005: Potential slashing evasion during re-delegationGHSA-86h5-xcpx-cfqc

Fix: cosmos/cosmos-sdk@7dbed2f

GHSA-86h5-xcpx-cfqc 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.

Also known asGO-2024-2584

Published

Feb 27, 2024

Updated

Nov 4, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2024 · 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

ASA-2024-005: Potential slashing evasion during re-delegation

Component: Cosmos SDK Criticality: Low Affected Versions: Cosmos SDK versions <= 0.50.4; <= 0.47.9 Affected Users: Chain developers, Validator and Node operators Impact: Slashing Evasion

Summary

An issue was identified in the slashing mechanism that may allow for the evasion of slashing penalties during a slashing event. If a delegation contributed to byzantine behavior of a validator, and the validator has not yet been slashed, it may be possible for that delegation to evade a pending slashing penalty through re-delegation behavior. Additional validation logic was added to restrict this behavior.

Next Steps for Impacted Parties

If you are a chain developer on an affected version of the Cosmos SDK, it is advised to update to the latest available version of the Cosmos SDK for your project. Once a patched version is available, it is recommended that network operators upgrade.

A Github Security Advisory for this issue is available in the Cosmos-SDK repository. For more information about Cosmos SDK, see https://docs.cosmos.network/.

This issue was found by cat shark (Khanh) who reported it to the Cosmos Bug Bounty Program on HackerOne on December 6, 2023. 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.50.0&&< 0.50.5	0.50.5`go get github.com/cosmos/cosmos-sdk@v0.50.5`
🐹Go	`github.com/cosmos/cosmos-sdk`	all versions	0.47.10`go get github.com/cosmos/cosmos-sdk@v0.47.10`

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.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86h5-xcpx-cfqc 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.

Frequently Asked Questions

## ASA-2024-005: Potential slashing evasion during re-delegation **Component**: Cosmos SDK **Criticality**: Low **Affected Versions**: Cosmos SDK versions <= 0.50.4; <= 0.47.9 **Affected Users**: Chain developers, Validator and Node operators **Impact**: Slashing Evasion ## Summary An issue was identified in the slashing mechanism that may allow for the evasion of slashing penalties during a slashing event. If a delegation contributed to byzantine behavior of a validator, and the validator has not yet been slashed, it may be possible for that delegation to evade a pending slashing penalty t

O3 Security · Impact-Aware SCA

Is GHSA-86h5-xcpx-cfqc in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works