wasmvm: Malicious smart contract can slow down block production

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.) Patch - 1.5: https://github.com/CosmWasm/cosmwasm/commit/2b7f2faa57a1efc8207455c37f87f1eee6035a27 - 2.0: https://github.com/CosmWasm/cosmwasm/commit/d6143b0aff16a39bbea4be37597d8e9d9b213d3b - 2.1: https://github.com/CosmWasm/cosmwasm/commit/f0c04c03cbe2557634c1bbcdc2ce203fe7caca58 - 2.2: https://github.com/CosmWasm/cosmwasm/commit/a5d62f65b5eb947ebe40e2085b1c48a9d0a244d0 Applying the patch The patch will be shipped in releases of wasmvm. You can update more or less as follows: 1. Check the current wasmvm version: go list -m…

Published by the source

4 Feb 2025, 18:57 UTC

Last modified by the source

9 Jul 2025, 16:06 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mx2j-7cmv-353c

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

# Patch Next advisory brief: GHSA-mx2j-7cmv-353c

Advisory: wasmvm: Malicious smart contract can slow down block production
IDs: GHSA-mx2j-7cmv-353c
Record: https://patchnext.com/advisories/ghsa-mx2j-7cmv-353c (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: cosmwasm-vm 2.2.1, 2.1.6, 2.0.9, 1.5.10; github.com/CosmWasm/wasmvm/v2 2.2.2, 2.1.5, 2.0.6-0.20250204103256-d62c3b826a9d, 2.0.6, 2.0.0-20250204103256-d62c3b826a9d; github.com/CosmWasm/wasmvm 1.5.8-0.20250204093451-1f4db20199b8, 1.5.8, 0.0.0-20250204093451-1f4db20199b8. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io cosmwasm-vm: affected >= 2.2.0, <= 2.2.0; >= 2.1.0, < 2.1.6; >= 2.0.0, < 2.0.9; < 1.5.10; fixed in 2.0.9, 1.5.10, 2.1.6, 2.2.1
- Go github.com/CosmWasm/wasmvm/v2: affected >= 2.2.0, < 2.2.2; >= 2.1.0, < 2.1.5; < 2.0.0-20250204103256-d62c3b826a9d; >= 2.0.0, <= 2.0.5; >= 2.0.6-0, < 2.0.6-0.20250204103256-d62c3b826a9d; fixed in 2.0.0-20250204103256-d62c3b826a9d, 2.0.6, 2.1.5, 2.2.2, 2.0.6-0.20250204103256-d62c3b826a9d
- Go github.com/CosmWasm/wasmvm: affected < 0.0.0-20250204093451-1f4db20199b8; >= 0.1.0, <= 1.5.7; >= 1.5.8-0, < 1.5.8-0.20250204093451-1f4db20199b8; fixed in 1.5.8-0.20250204093451-1f4db20199b8, 1.5.8, 0.0.0-20250204093451-1f4db20199b8

## Suggested inspection (read-only)
- crates.io cosmwasm-vm: check the installed version with your package manager.
- Go github.com/CosmWasm/wasmvm/v2: check the installed version with your package manager.
- Go github.com/CosmWasm/wasmvm: 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 cosmwasm-vm, github.com/CosmWasm/wasmvm/v2, github.com/CosmWasm/wasmvm.
- 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-mx2j-7cmv-353c (GitHub-reviewed advisory GHSA-mx2j-7cmv-353c lists affected ranges: crates.io cosmwasm-vm >=2.2.0 =2.1.0 =2.0.0 =0 =2.2.0 =2.1.0 =0 =2.0.0 =2.0.6-0 =0 =0.1.0 =1.5.8-0 <1.5.8-0.20250204093451-1f4db20199b8)

Commands are suggestions: review each one before running it.