Contract balance not updating correctly after interchain transaction

Exploitation

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

CVSS

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

EPSS

• CVE-2024-37153: 0.62% estimated exploitation activity in the next 30 days; percentile 49.67 (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.

Summary Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server. Details We discovered a bug walking through how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the sender parameter in an ICS20 transfer using the ICS20 precompile Proof of Concept Impact This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction. Severity Based on ImmuneFi Severity Classification System the severity was evaluated to Critical since the attack could have lead to create new supply of EVMOS and therefore lead to Direct loss of funds's value. Patches The issue has been patched in versions =V18.1.0. For more…

Published by the source

6 Jun 2024, 18:51 UTC

Last modified by the source

17 Jun 2024, 15:23 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xgr7-jgq3-mhmc

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

# Patch Next advisory brief: CVE-2024-37153

Advisory: Contract balance not updating correctly after interchain transaction
IDs: CVE-2024-37153, GHSA-xgr7-jgq3-mhmc
Record: https://patchnext.com/advisories/cve-2024-37153 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/evmos/evmos/v10 18.1.0; github.com/evmos/evmos/v15 18.1.0; github.com/evmos/evmos/v6 18.1.0; github.com/evmos/evmos/v7 18.1.0; github.com/evmos/evmos/v16 18.1.0; github.com/evmos/evmos/v18 18.1.0; github.com/evmos/evmos/v13 18.1.0; github.com/evmos/evmos/v14 18.1.0; github.com/evmos/evmos/v17 18.1.0; github.com/evmos/evmos/v8 18.1.0; github.com/evmos/evmos/v12 18.1.0; github.com/evmos/evmos/v9 18.1.0; github.com/evmos/evmos/v11 18.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/evmos/evmos/v10: affected <= 10.0.1; fixed in 18.1.0
- Go github.com/evmos/evmos/v15: affected <= 15.0.0; fixed in 18.1.0
- Go github.com/evmos/evmos/v6: affected <= 6.0.4; fixed in 18.1.0
- Go github.com/evmos/evmos/v7: affected <= 7.0.0; fixed in 18.1.0
- Go github.com/evmos/evmos/v16: affected <= 16.0.4; fixed in 18.1.0
- Go github.com/evmos/evmos/v18: affected <= 18.0.0; fixed in 18.1.0
- Go github.com/evmos/evmos/v13: affected <= 13.0.2; fixed in 18.1.0
- Go github.com/evmos/evmos/v14: affected <= 14.1.0; fixed in 18.1.0
- Go github.com/evmos/evmos/v17: affected <= 17.0.1; fixed in 18.1.0
- Go github.com/evmos/evmos/v8: affected <= 8.2.3; fixed in 18.1.0
- Go github.com/evmos/evmos/v12: affected <= 12.1.6; fixed in 18.1.0
- Go github.com/evmos/evmos/v9: affected <= 9.1.0; fixed in 18.1.0
- Go github.com/evmos/evmos/v11: affected <= 11.0.2; fixed in 18.1.0

## Suggested inspection (read-only)
- Go github.com/evmos/evmos/v10: check the installed version with your package manager.
- Go github.com/evmos/evmos/v15: 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/evmos/evmos/v18: check the installed version with your package manager.
- Go github.com/evmos/evmos/v13: check the installed version with your package manager.
- Go github.com/evmos/evmos/v14: check the installed version with your package manager.
- Go github.com/evmos/evmos/v17: check the installed version with your package manager.
- Go github.com/evmos/evmos/v8: check the installed version with your package manager.
- Go github.com/evmos/evmos/v12: check the installed version with your package manager.
- Go github.com/evmos/evmos/v9: check the installed version with your package manager.
- Go github.com/evmos/evmos/v11: 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/evmos/evmos/v10, github.com/evmos/evmos/v15, github.com/evmos/evmos/v6, github.com/evmos/evmos/v7, github.com/evmos/evmos/v16, github.com/evmos/evmos/v18, github.com/evmos/evmos/v13, github.com/evmos/evmos/v14, github.com/evmos/evmos/v17, github.com/evmos/evmos/v8, github.com/evmos/evmos/v12, github.com/evmos/evmos/v9, github.com/evmos/evmos/v11.
- 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-xgr7-jgq3-mhmc (GitHub-reviewed advisory GHSA-xgr7-jgq3-mhmc lists affected ranges: Go github.com/evmos/evmos/v18 >=0 =0 =0 =0 =0 =0 =0 =0 =0 =0…)

Commands are suggestions: review each one before running it.