GHSA-54gx-3cgr-7mfm: Cosmos EVM: incorrect state handling during nested EVM execution paths
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/cosmos/evm (Go) 0.6.0.
Low priority for now. Upgrade to github.com/cosmos/evm (Go) 0.6.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
**Advisory ID:** ASA-2026-002 **Component:** ICS20 Precompile **Status:** Resolved **Published:** March 2026 **Contact:** [security@cosmoslabs.io](mailto: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](https://github.com/cosmos/evm/releases/tag/v0.6.0).** | Field | Value | | --- | --- | | **Severity** | Critical | | **Affected Component** | ICS20 Precompile | | **Affected Versions** | Cosmos EVM implementations including the ICS20 precompile | | **Patched Version** | [v0.6.0](https://github.com/cosmos/evm/releases/tag/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 investigation and response process and thank our ecosystem partners for their support in coordinating mitigation and validation efforts. --- ## Remediation Summary On January 21, 2026, Cosmos Labs was notified of suspicious activity on a network running the affected implementation. The issue resulted in financial loss on the Saga EVM network. After confirming the vulnerability, Cosmos Labs coordinated with the affected chain team and ecosystem partners to investigate the issue, deploy mitigations, and assist other chains running the affected code. Cosmos Labs contacted chains known to be running versions containing the affected component to verify their configurations and support mitigation where necessary. At the time of publication, all known affected chains have either applied mitigations or upgraded to a patched version. --- ## Root Cause The vulnerability was caused by incorrect state handling during nested EVM execution paths involving the ICS20 precompile. Under certain execution conditions, state updates performed during recursive calls were not correctly reflected in the outer execution context. This could allow repeated use of the same token balance within a single transaction. --- ## Mitigation As an immediate mitigation, chains were advised to disable the ICS20 precompile through a coordinated upgrade. Cosmos Labs assisted ecosystem teams in verifying whether their chains were affected and in applying the mitigation where required. - 15 chains were identified as running code containing the issue - 6 chains did not have the affected feature enabled - The remaining chains implemented the mitigation before exploitation occurred - 1 chain experienced an exploit prior to mitigation --- ## Long-Term Fix A permanent fix was implemented to ensure state consistency across nested EVM execution paths. The patch was distributed privately to affected teams for validation and later released publicly. The fix is included in **[v0.6.0](https://github.com/cosmos/evm/releases/tag/v0.6.0)**. --- ## Am I Affected? Chains may be affected if they: - Run versions of the Cosmos EVM stack that include the ICS20 precompile implementation - Have the ICS20 precompile enabled - Have not upgraded to **v0.6.0** or applied the mitigation Chains that have upgraded to **v0.6.0** or have disabled the ICS20 precompile are **not vulnerable to this issue**. If you are unsure whether your chain is affected, please contact: **[security@cosmoslabs.io](mailto:security@cosmoslabs.io)** --- ## Timeline **July 2024** The code containing the vulnerability was introduced upstream. **January 21, 2026** A network running the affected implementation experienced an exploit. The incident resulted in an estimated loss of approximately **$7M** on that network. **January 21, 2026** Cosmos Labs was notified of the potential vulnerability and began investigating. **January 21–22, 2026** The issue was reproduced and an initial mitigation was identified. **Late January 2026** Root cause analysis was conducted and a long-term fix was developed. **Early February 2026** The fix was validated internally and shared privately with affected ecosystem teams for review and testing. **Mid February 2026** Patches and mitigation guidance were distributed to chains running affected code. **March 2026** The permanent fix was released publicly as part of **v0.6.0**. --- ## Acknowledgements We would like to thank the teams and security partners who collaborated with us during the investigation and remediation process, including contributors from: - Saga - B-Harvest - Mantra - Zellic - Sherlock Their collaboration and responsiveness helped accelerate investigation, validation of the fix, and coordinated mitigation across affected chains. --- ## Strengthening Security Processes Following this incident, Cosmos Labs is implementing several improvements to further strengthen the security of the Cosmos EVM stack, including: - Expanded fuzz testing focused on complex execution paths - Additional auditing of state management logic across EVM integrations - Improvements to testing frameworks for precompile functionality - Continued collaboration with ecosystem security partners - Increased our bug bounty payouts for our [security program](https://hackerone.com/cosmos) These improvements are designed to reduce the likelihood of similar issues and ensure that teams building on the Cosmos stack can continue to rely on secure and well-tested infrastructure. --- ## Disclosure and Coordination Cosmos Labs coordinated with ecosystem partners and affected teams to investigate the issue, validate mitigations, and distribute the permanent fix prior to public disclosure. We appreciate the collaboration of ecosystem teams who assisted with investigation, validation, and responsible remediation of this issue. --- ## Responsible Disclosure Cosmos Labs encourages responsible disclosure of potential vulnerabilities. Security researchers who discover a potential issue are encouraged to report it privately so it can be investigated and addressed responsibly. Reports can be submitted to: **[security@cosmoslabs.io](mailto:security@cosmoslabs.io)** Information about Cosmos Labs security programs and responsible disclosure practices, including bug bounty opportunities, will be made available through Cosmos Labs security channels, which can be signed up for [here](https://docs.google.com/forms/d/1Ae6ruTAw9zRoeN0xFxNbTfS-xCFdO68NGRsyFAeWHMc/edit).
- Published
- Mar 11, 2026
- Updated
- Mar 23, 2026
- EPSS
- —
- CWE
- CWE-670
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/cosmos/evm | pkg:golang/github.com/cosmos/evm |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/cosmos/evm | before 0.6.0 | 0.6.0 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GO-2026-4677Cosmos EVM: incorrect state handling during nested EVM execution paths in github.com/cosmos/evm0Monitor
- GO-2025-4041Cosmos EVM Vulnerability in github.com/cosmos/evm0Monitor
- GHSA-8pfh-j44r-f654Cosmos EVM Vulnerability0Monitor
Published before and after this one in the same product
- ← EarlierGHSA-mjfq-3qr2-6g84May 14, 2025 · Cosmos EVM Allows Partial Precompile State Writes0Monitor
- ← EarlierGO-2025-3684May 15, 2025 · Cosmos EVM Allows Partial Precompile State Writes in github.com/cosmos/evm0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/cosmos/evm | 0.6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
Weakness class (CWE)
CWE-670 · Always-Incorrect Control Flow ImplementationCVSS vector
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
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Fix✗ → ✓
- CVSS9.5 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.