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

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

27 Feb 2024, 21:55 UTC

Last modified by the source

17 Mar 2026, 05:03 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-86h5-xcpx-cfqc

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

# Patch Next advisory brief: GHSA-86h5-xcpx-cfqc

Advisory: ASA-2024-005: Potential slashing evasion during re-delegation
IDs: GHSA-86h5-xcpx-cfqc
Record: https://patchnext.com/advisories/ghsa-86h5-xcpx-cfqc (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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.5, 0.47.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cosmos/cosmos-sdk: affected >= 0.50.0, <= 0.50.4; <= 0.47.9; fixed in 0.47.10, 0.50.5

## 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-86h5-xcpx-cfqc (GitHub-reviewed advisory GHSA-86h5-xcpx-cfqc lists affected ranges: Go github.com/cosmos/cosmos-sdk >=0.50.0 =0 <=0.47.9)

Commands are suggestions: review each one before running it.