Read the docs
TI-2024-21526 Aliases CVE-2024-32644GHSA-3fp5-2xwh-fxm6

Evmos' transaction execution not accounting for all state transition after interaction with precompiles

Priority MEDIUM 49CWE-662Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.

Summary

Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is based on the fact that to sync the Cosmos SDK state and the EVM one, we rely on the `stateDB.Commit()` method. When we call this method, we iterate though all the `dirtyStorage` and, **if and only if** it is different than the `originStorage`, we set the new state. Setting the new state means we update the Cosmos SDK KVStore. If a contract storage state that is the same before and after a transaction, but is changed during the transaction and can call an external contract after the change, it can be exploited to make the transaction similar to non-atomic. The vulnerability is **critical** since this could lead to drain of funds through creative SC interactions. The issue has been patched in versions >=V17.0.0.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00943 61st percentileScored 2026-11-07
Fix Fixed evmos (evmos): 17.0.0github.com/evmos/evmos/v16 (Go): 17.0.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
evmosevmosbefore 17.0.017.0.0Patch availableCNA
—github.com/evmos/evmos/v16 (Go)before 17.0.017.0.0Patch availableGHSA-3fp5-2xwh-fxm6
—github.com/evmos/evmos/v7 (Go)up to 7.0.0—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/evmos/evmos/v6 (Go)up to 6.0.4—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/evmos/evmos/v5 (Go)up to 5.0.0—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/tharsis/evmos (Go)up to 1.1.3—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/tharsis/evmos/v2 (Go)up to 2.0.2—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/tharsis/evmos/v3 (Go)up to 3.0.3—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/tharsis/evmos/v4 (Go)up to 4.0.2—No fix listedGHSA-3fp5-2xwh-fxm6
—github.com/tharsis/evmos/v5 (Go)up to 5.0.1—No fix listedGHSA-3fp5-2xwh-fxm6
  • evmos Vendorevmos Affected before 17.0.0 Fixed in 17.0.0 Patch available CNA
  • github.com/evmos/evmos/v16 (Go) Vendor— Affected before 17.0.0 Fixed in 17.0.0 Patch available GHSA-3fp5-2xwh-fxm6
  • github.com/evmos/evmos/v7 (Go) Vendor— Affected up to 7.0.0 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/evmos/evmos/v6 (Go) Vendor— Affected up to 6.0.4 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/evmos/evmos/v5 (Go) Vendor— Affected up to 5.0.0 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/tharsis/evmos (Go) Vendor— Affected up to 1.1.3 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/tharsis/evmos/v2 (Go) Vendor— Affected up to 2.0.2 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/tharsis/evmos/v3 (Go) Vendor— Affected up to 3.0.3 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/tharsis/evmos/v4 (Go) Vendor— Affected up to 4.0.2 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6
  • github.com/tharsis/evmos/v5 (Go) Vendor— Affected up to 5.0.1 Fixed in — No fix listed GHSA-3fp5-2xwh-fxm6

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:evmos:evmos:*:*:*:*:*:*:*:*before 17.0.0Vulnerableevmos
  • cpe:2.3:a:evmos:evmos:*:*:*:*:*:*:*:* Versions before 17.0.0 Vulnerable ·evmos

Remediation

  • Fix · CNA evmos (evmos) Fixed in 17.0.0
  • Fix · GHSA-3fp5-2xwh-fxm6 github.com/evmos/evmos/v16 (Go) Fixed in 17.0.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-32644
  2. 2026-10-03 Alias added: GHSA-3fp5-2xwh-fxm6

References

Patch 1

Advisory 2

Other 4

  • TI-2022-16363 Ethermint DoS through Unintended Contract Selfdestruct CVSS 3.1HIGH 8.2
  • TI-2024-24680 Evmos's contract balance not updating correctly after interchain transaction CVSS 3.1HIGH 7.5
  • TI-2024-26619 Evmos vulnerable to exploit of smart contract account and vesting CVSS 3.1HIGH 8.8
  • TI-2022-08552 Account compromise in Evmos CVSS 3.1HIGH 8.1
  • TI-2024-24685 Evmos is missing precompile checks CVSS 3.1HIGH 8.1
  • TI-2024-24681 Evmos allows unvested token delegations CVSS 3.1MEDIUM 5.3
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences