Skip to content

← Public intelligence

Go package

github.com/cosmos/evm

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.3GoPublished

    Cosmos EVM: incorrect state handling during nested EVM execution paths

    GHSA-54gx-3cgr-7mfm

    Affected
    • Go github.com/cosmos/evm < 0.6.0
    Fixed in
    0.6.0· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 0.6.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedGoPublished

    Cosmos EVM Vulnerability

    GHSA-8pfh-j44r-f654

    Affected
    • Go github.com/cosmos/evm >= 0.3.0, < 0.3.2; >= 0.4.0, < 0.4.2
    Fixed in
    0.3.20.4.2· Vendor fix available
    Issue
    Patches Patched in versions v0.3.1, v0.4.2, and in the v0.5.0 release. More information will be disclosed at a later point to ensure chains have time to safely upgrade. Workarounds No workarounds for chains that make use of static or dynamic precompiles. Upgrading is strongly recommended. Testing Tests are introduced in every affected version. Credits Special thanks to @yihuang for the help on this issue.

    Recommended action: Upgrade to 0.4.2 or 0.3.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →