Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Go package github.com/cosmos/cosmos-sdk module x/crisis does NOT cause chain halt

GHSA-qfc5-6r3j-jj22

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/cosmos/cosmos-sdk

    Affected
    <= 0.47.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

x/crisis does NOT cause chain halt Impact If an invariant check fails on a Cosmos SDK network and a transaction is sent to the x/crisis module to halt the chain, the chain does not halt. All versions of the x/crisis module is affected on all versions of the Cosmos SDK. Details The x/crisis module is supposed to allow anyone to halt a chain in the event of a violated invariant by sending a MsgVerifyInvariant with the name of the invariant. Processing this message is supposed to cause the nodes to panic. However, because the panic is within a transaction, it is caught by the SDK’s built-in panic-recovery machinery and just treated as a normal “invalid” transaction (ie. it returns a non-zero abci Code). Thus the x/crisis transactions don’t actually cause chains to halt. If there is an invariant violation, it can be confirmed with an x/crisis transaction, but it won’t cause any nodes to halt, they will just continue processing blocks. That said, any node running with start…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-qfc5-6r3j-jj22

Agent brief

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

# Patch Next advisory brief: GHSA-qfc5-6r3j-jj22

Advisory: Go package github.com/cosmos/cosmos-sdk module x/crisis does NOT cause chain halt
IDs: GHSA-qfc5-6r3j-jj22
Record: https://patchnext.com/advisories/ghsa-qfc5-6r3j-jj22 (revision 1, source checked 26 Oct 2026, 14:58 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cosmos/cosmos-sdk: affected <= 0.47.2

## Suggested inspection (read-only)
- Go github.com/cosmos/cosmos-sdk: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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-qfc5-6r3j-jj22 (GitHub-reviewed advisory GHSA-qfc5-6r3j-jj22 lists affected ranges: Go github.com/cosmos/cosmos-sdk >=0 <=0.47.2)

Commands are suggestions: review each one before running it.

Loading voting…