Cosmos EVM: incorrect state handling during nested EVM execution paths

Exploitation

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

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Advisory ID: ASA-2026-002 Component: ICS20 Precompile Status: Resolved Published: March 2026 Contact: security@cosmoslabs.io --- Security Advisory ASA-2026-002 Status: Resolved. A patch is available and all known affected chains have either applied mitigations or upgraded. | Field | Value | | --- | --- | | Severity | Critical | | Affected Component | ICS20 Precompile | | Affected Versions | Cosmos EVM implementations including the ICS20 precompile | | Patched Version | v0.6.0 | | First Reported | January 21, 2026 | | Public Disclosure | March 2026 | --- Introduction Recently, there was a vulnerability affecting a feature used by some chains built on the Cosmos EVM stack. Working together with ecosystem partners and affected teams, particularly Saga, B-Harvest, Mantra, Zellic and Sherlock, Cosmos Labs investigated the issue, coordinated mitigations, developed a permanent fix, and issued a patch to affected chains. We appreciate the collaboration of the teams who assisted during the…

Published by the source

11 Mar 2026, 14:53 UTC

Last modified by the source

11 Mar 2026, 14:53 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-54gx-3cgr-7mfm

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

# Patch Next advisory brief: GHSA-54gx-3cgr-7mfm

Advisory: Cosmos EVM: incorrect state handling during nested EVM execution paths
IDs: GHSA-54gx-3cgr-7mfm
Record: https://patchnext.com/advisories/ghsa-54gx-3cgr-7mfm (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
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/evm 0.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cosmos/evm: affected < 0.6.0; fixed in 0.6.0

## Suggested inspection (read-only)
- Go github.com/cosmos/evm: 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/evm.
- 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-54gx-3cgr-7mfm (GitHub-reviewed advisory GHSA-54gx-3cgr-7mfm lists affected ranges: Go github.com/cosmos/evm >=0 <0.6.0)

Commands are suggestions: review each one before running it.