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

Exploitation

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

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS

• CVE-2024-32644: 0.94% estimated exploitation activity in the next 30 days; percentile 61.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Context - stateObject: represents the state of an account and is used to store its updates during a state transition. This is accomplished using two in memory Storage variables: originStorage and dirtyStorage - StateDB: it is the general interface to retrieve accounts and holds a map of stateObjects. Impact An external contributor, @iczc, discovered 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. Below, are described the steps to perform the attack: - User send a tx to a smart contract (SC) that is calling a precompile. - The SC perform a state transition of its state from…

Published by the source

10 Apr 2024, 22:04 UTC

Last modified by the source

19 Apr 2024, 16:21 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3fp5-2xwh-fxm6

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

# Patch Next advisory brief: CVE-2024-32644

Advisory: Evmos transaction execution not accounting for all state transition after interaction with precompiles
IDs: CVE-2024-32644, GHSA-3fp5-2xwh-fxm6
Record: https://patchnext.com/advisories/cve-2024-32644 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/evmos/evmos/v16 17.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tharsis/evmos/v4: affected <= 4.0.2
- Go github.com/tharsis/evmos/v3: affected <= 3.0.3
- Go github.com/tharsis/evmos/v2: affected <= 2.0.2
- Go github.com/evmos/evmos/v5: affected <= 5.0.0
- Go github.com/tharsis/evmos: affected <= 1.1.3
- Go github.com/evmos/evmos/v6: affected <= 6.0.4
- Go github.com/evmos/evmos/v7: affected <= 7.0.0
- Go github.com/evmos/evmos/v16: affected <= 16.0.4; fixed in 17.0.0
- Go github.com/tharsis/evmos/v5: affected <= 5.0.1

## Suggested inspection (read-only)
- Go github.com/tharsis/evmos/v4: check the installed version with your package manager.
- Go github.com/tharsis/evmos/v3: check the installed version with your package manager.
- Go github.com/tharsis/evmos/v2: check the installed version with your package manager.
- Go github.com/evmos/evmos/v5: check the installed version with your package manager.
- Go github.com/tharsis/evmos: check the installed version with your package manager.
- Go github.com/evmos/evmos/v6: check the installed version with your package manager.
- Go github.com/evmos/evmos/v7: check the installed version with your package manager.
- Go github.com/evmos/evmos/v16: check the installed version with your package manager.
- Go github.com/tharsis/evmos/v5: 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/tharsis/evmos/v4, github.com/tharsis/evmos/v3, github.com/tharsis/evmos/v2, github.com/evmos/evmos/v5, github.com/tharsis/evmos, github.com/evmos/evmos/v6, github.com/evmos/evmos/v7, github.com/evmos/evmos/v16, github.com/tharsis/evmos/v5.
- 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-3fp5-2xwh-fxm6 (GitHub-reviewed advisory GHSA-3fp5-2xwh-fxm6 lists affected ranges: Go github.com/evmos/evmos/v16 >=0 =0 =0 =0 =0 =0 =0 =0 =0 <=5.0.1)

Commands are suggestions: review each one before running it.