Gas mispricing in cosmwasm-vm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (cosmwasm-vm 2.1.2, 2.0.5, 1.5.6; github.com/CosmWasm/wasmvm/v2 2.1.2, 2.0.3; github.com/CosmWasm/wasmvm 1.5.4), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io cosmwasm-vm
- Affected
- < 1.5.6>= 2.0.0, < 2.0.5>= 2.1.0, < 2.1.2
- Fixed in
- 2.1.2, 1.5.6, 2.0.5
Go github.com/CosmWasm/wasmvm/v2
- Affected
- >= 2.1.0, < 2.1.2>= 2.0.0, < 2.0.3
- Fixed in
- 2.0.3, 2.1.2
- Affected
- < 1.5.4
- Fixed in
- 1.5.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rg2q-2jh9-447q lists affected ranges: crates.io cosmwasm-vm >=0 =2.0.0 =2.1.0 =2.1.0 =2.0.0 =0 <1.5.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Component: wasmvm Criticality: Medium (ACMv1: I:Moderate; L:Likely) Patched versions: wasmvm 1.5.4, 2.0.3, 2.1.2 Some Wasm operations take significantly more gas than our benchmarks indicated. This can lead to missing the gas target we defined by a factor of ~10x. This means a malicious contract could take 10 times as much time to execute as expected, which can be used to temporarily DoS a chain. See CWA-2024-004 for more details.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-rg2q-2jh9-447q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-rg2q-2jh9-447q Advisory: Gas mispricing in cosmwasm-vm IDs: GHSA-rg2q-2jh9-447q Record: https://patchnext.com/advisories/ghsa-rg2q-2jh9-447q (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: Medium (CVSS 5.3) 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.1.2, 2.0.5, 1.5.6; github.com/CosmWasm/wasmvm/v2 2.1.2, 2.0.3; github.com/CosmWasm/wasmvm 1.5.4. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io cosmwasm-vm: affected < 1.5.6; >= 2.0.0, < 2.0.5; >= 2.1.0, < 2.1.2; fixed in 2.1.2, 1.5.6, 2.0.5 - Go github.com/CosmWasm/wasmvm/v2: affected >= 2.1.0, < 2.1.2; >= 2.0.0, < 2.0.3; fixed in 2.0.3, 2.1.2 - Go github.com/CosmWasm/wasmvm: affected < 1.5.4; fixed in 1.5.4 ## 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-rg2q-2jh9-447q (GitHub-reviewed advisory GHSA-rg2q-2jh9-447q lists affected ranges: crates.io cosmwasm-vm >=0 =2.0.0 =2.1.0 =2.1.0 =2.0.0 =0 <1.5.4) Commands are suggestions: review each one before running it.
Loading voting…