What is GHSA-MX2J-7CMV-353C?

GHSA-MX2J-7CMV-353C is a medium-severity security vulnerability in cosmwasm-vm (rust), affecting versions = 2.2.0. It is fixed in 2.2.1, 2.1.6, 2.0.9, 1.5.10, 2.2.2, 2.1.5, 0.0.0-20250204093451-1f4db20199b8, 2.0.0-20250204103256-d62c3b826a9d, 1.5.8, 2.0.6, 1.5.8-0.20250204093451-1f4db20199b8, 2.0.6-0.20250204103256-d62c3b826a9d.

Which packages are affected by GHSA-MX2J-7CMV-353C?

cosmwasm-vm (rust) versions = 2.2.0; github.com/CosmWasm/wasmvm/v2 (go) versions >= 2.2.0, < 2.2.2; github.com/CosmWasm/wasmvm (go) versions < 0.0.0-20250204093451-1f4db20199b8.

Is there a fix for GHSA-MX2J-7CMV-353C?

Yes. GHSA-MX2J-7CMV-353C is fixed in 2.2.1, 2.1.6, 2.0.9, 1.5.10, 2.2.2, 2.1.5, 0.0.0-20250204093451-1f4db20199b8, 2.0.0-20250204103256-d62c3b826a9d, 1.5.8, 2.0.6, 1.5.8-0.20250204093451-1f4db20199b8, 2.0.6-0.20250204103256-d62c3b826a9d. Upgrade to this version or later.

Is GHSA-MX2J-7CMV-353C exploitable, and should I be worried?

Whether GHSA-MX2J-7CMV-353C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-MX2J-7CMV-353C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-MX2J-7CMV-353C?

Upgrade: cosmwasm-vm to 2.2.1 or later, cosmwasm-vm to 2.1.6 or later, cosmwasm-vm to 2.0.9 or later, cosmwasm-vm to 1.5.10 or later, github.com/CosmWasm/wasmvm/v2 to 2.2.2 or later, github.com/CosmWasm/wasmvm/v2 to 2.1.5 or later, github.com/CosmWasm/wasmvm to 0.0.0-20250204093451-1f4db20199b8 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.0-20250204103256-d62c3b826a9d or later, github.com/CosmWasm/wasmvm to 1.5.8 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.6 or later, github.com/CosmWasm/wasmvm to 1.5.8-0.20250204093451-1f4db20199b8 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.6-0.20250204103256-d62c3b826a9d or later.

GHSA-MX2J-7CMV-353C in cosmwasm-vm

Q: Is there a fix for GHSA-MX2J-7CMV-353C?

Yes. GHSA-MX2J-7CMV-353C is fixed in 2.2.1, 2.1.6, 2.0.9, 1.5.10, 2.2.2, 2.1.5, 0.0.0-20250204093451-1f4db20199b8, 2.0.0-20250204103256-d62c3b826a9d, 1.5.8, 2.0.6, 1.5.8-0.20250204093451-1f4db20199b8, 2.0.6-0.20250204103256-d62c3b826a9d. Upgrade to this version or later.

Q: Is GHSA-MX2J-7CMV-353C exploitable, and should I be worried?

Whether GHSA-MX2J-7CMV-353C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-MX2J-7CMV-353C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-MX2J-7CMV-353C?

Upgrade: cosmwasm-vm to 2.2.1 or later, cosmwasm-vm to 2.1.6 or later, cosmwasm-vm to 2.0.9 or later, cosmwasm-vm to 1.5.10 or later, github.com/CosmWasm/wasmvm/v2 to 2.2.2 or later, github.com/CosmWasm/wasmvm/v2 to 2.1.5 or later, github.com/CosmWasm/wasmvm to 0.0.0-20250204093451-1f4db20199b8 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.0-20250204103256-d62c3b826a9d or later, github.com/CosmWasm/wasmvm to 1.5.8 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.6 or later, github.com/CosmWasm/wasmvm to 1.5.8-0.20250204093451-1f4db20199b8 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.6-0.20250204103256-d62c3b826a9d or later.

Summary

wasmvm: Malicious smart contract can slow down block production

CWA-2025-002

Severity

Medium (Moderate + Likely)[^1]

Affected versions:

wasmvm >= 2.2.0, < 2.2.2
wasmvm >= 2.1.0, < 2.1.5
wasmvm >= 2.0.0, < 2.0.6
wasmvm < 1.5.8

Patched versions:

wasmvm 1.5.8, 2.0.6, 2.1.5, 2.2.2

Description of the bug

The vulnerability can be used to slow down block production. The attack requires a malicious contract,
so permissioned chains are unlikely to be affected.

(We'll add more detail once chains had a chance to upgrade.)

Applying the patch

The patch will be shipped in releases of wasmvm. You can update more or less as follows:

Check the current wasmvm version: go list -m github.com/CosmWasm/wasmvm
Bump the github.com/CosmWasm/wasmvm dependency in your go.mod to one of the patched version
depending on which minor version you are on; go mod tidy; commit.
If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, update them accordingly.
Check the updated wasmvm version: go list -m github.com/CosmWasm/wasmvm and ensure you see 1.5.8, 2.0.6, 2.1.5 or 2.2.2.
Follow your regular practices to deploy chain upgrades.

The patch is consensus breaking and requires a coordinated upgrade.

Acknowledgement

This issue was found by meadow101 who reported it to the Cosmos Bug Bounty Program on HackerOne.

If you believe you have found a bug in the Interchain Stack or would like to contribute to the
program by reporting a bug, please see https://hackerone.com/cosmos.

Timeline

2024-11-24: Confio receives a report through the Cosmos bug bounty program maintained by Amulet.
2024-12-20: Confio security contributors confirm the report.
2024-01-27: Confio developed the patch internally.
2025-02-04: Patch gets released.

[^1]: following Amulet's Severity Classification Framework ACMv1.2: https://github.com/interchainio/security/blob/0295254e8645301ccb606d46108a45cede0a73e0/resources/CLASSIFICATION_MATRIX.md

Impact

Affected versions

cosmwasm-vm (= 2.2.0) cosmwasm-vm (>= 2.1.0, < 2.1.6) cosmwasm-vm (>= 2.0.0, < 2.0.9) cosmwasm-vm (< 1.5.10) github.com/CosmWasm/wasmvm/v2 (>= 2.2.0, < 2.2.2) github.com/CosmWasm/wasmvm/v2 (>= 2.1.0, < 2.1.5) github.com/CosmWasm/wasmvm (< 0.0.0-20250204093451-1f4db20199b8) github.com/CosmWasm/wasmvm/v2 (< 2.0.0-20250204103256-d62c3b826a9d) github.com/CosmWasm/wasmvm (>= 0.1.0, <= 1.5.7) github.com/CosmWasm/wasmvm/v2 (>= 2.0.0, <= 2.0.5) github.com/CosmWasm/wasmvm (>= 1.5.8-0, < 1.5.8-0.20250204093451-1f4db20199b8) github.com/CosmWasm/wasmvm/v2 (>= 2.0.6-0, < 2.0.6-0.20250204103256-d62c3b826a9d)

Security releases

cosmwasm-vm → 2.2.1 (rust) cosmwasm-vm → 2.1.6 (rust) cosmwasm-vm → 2.0.9 (rust) cosmwasm-vm → 1.5.10 (rust) github.com/CosmWasm/wasmvm/v2 → 2.2.2 (go) github.com/CosmWasm/wasmvm/v2 → 2.1.5 (go) github.com/CosmWasm/wasmvm → 0.0.0-20250204093451-1f4db20199b8 (go) github.com/CosmWasm/wasmvm/v2 → 2.0.0-20250204103256-d62c3b826a9d (go) github.com/CosmWasm/wasmvm → 1.5.8 (go) github.com/CosmWasm/wasmvm/v2 → 2.0.6 (go) github.com/CosmWasm/wasmvm → 1.5.8-0.20250204093451-1f4db20199b8 (go) github.com/CosmWasm/wasmvm/v2 → 2.0.6-0.20250204103256-d62c3b826a9d (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Frequently Asked Questions

What is GHSA-MX2J-7CMV-353C? GHSA-MX2J-7CMV-353C is a medium-severity security vulnerability in cosmwasm-vm (rust), affecting versions = 2.2.0. It is fixed in 2.2.1, 2.1.6, 2.0.9, 1.5.10, 2.2.2, 2.1.5, 0.0.0-20250204093451-1f4db20199b8, 2.0.0-20250204103256-d62c3b826a9d, 1.5.8, 2.0.6, 1.5.8-0.20250204093451-1f4db20199b8, 2.0.6-0.20250204103256-d62c3b826a9d.
Which packages are affected by GHSA-MX2J-7CMV-353C?
- cosmwasm-vm (rust) (versions = 2.2.0)
- github.com/CosmWasm/wasmvm/v2 (go) (versions >= 2.2.0, < 2.2.2)
- github.com/CosmWasm/wasmvm (go) (versions < 0.0.0-20250204093451-1f4db20199b8)
Is there a fix for GHSA-MX2J-7CMV-353C? Yes. GHSA-MX2J-7CMV-353C is fixed in 2.2.1, 2.1.6, 2.0.9, 1.5.10, 2.2.2, 2.1.5, 0.0.0-20250204093451-1f4db20199b8, 2.0.0-20250204103256-d62c3b826a9d, 1.5.8, 2.0.6, 1.5.8-0.20250204093451-1f4db20199b8, 2.0.6-0.20250204103256-d62c3b826a9d. Upgrade to this version or later.
Is GHSA-MX2J-7CMV-353C exploitable, and should I be worried? Whether GHSA-MX2J-7CMV-353C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-MX2J-7CMV-353C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-MX2J-7CMV-353C?
- Upgrade cosmwasm-vm to 2.2.1 or later
- Upgrade cosmwasm-vm to 2.1.6 or later
- Upgrade cosmwasm-vm to 2.0.9 or later
- Upgrade cosmwasm-vm to 1.5.10 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.2.2 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.1.5 or later
- Upgrade github.com/CosmWasm/wasmvm to 0.0.0-20250204093451-1f4db20199b8 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.0.0-20250204103256-d62c3b826a9d or later
- Upgrade github.com/CosmWasm/wasmvm to 1.5.8 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.0.6 or later
- Upgrade github.com/CosmWasm/wasmvm to 1.5.8-0.20250204093451-1f4db20199b8 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.0.6-0.20250204103256-d62c3b826a9d or later

Other vulnerabilities in cosmwasm-vm

CVE-IDSeverityPackage summary

GHSA-2Q97-M5RC-P3GPMediumgithub.com/CosmWasm/wasmvm/v2: CosmWasm VM Incorrect metering GHSA-VMQH-5232-V43RMediumgithub.com/CosmWasm/wasmvm/v2: Panic in wasmvm can slow down block production GHSA-75QH-GG76-P2W4Mediumcosmwasm-vm: CWA-2023-004: Excessive number of function parameters in compiled Wasm GHSA-RG2Q-2JH9-447QMediumcosmwasm-vm: Gas mispricing in cosmwasm-vm