Simulation of Wasmd message can cause crashing

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-2024-009 Severity Low (Marginal + Likely)[^1] Affected versions: - wasmd < 0.53.1 Patched versions: - wasmd 0.53.2 (please note that wasmd 0.53.1 is broken and must not be used) Description of the bug (Blank for now. We'll add more detail once chains had a chance to upgrade.) Mitigations Apart from upgrading, it is recommended to not open the gRPC and REST APIs of validator nodes to the public internet. Use isolated and resource-constrained environments for running separate public RPC nodes instead. These can then easily be thrown away and replaced with new instances in case of problems. Applying the patch Official Wasmd patch The patch will be shipped in a wasmd release. You will also have to update libwasmvm if you build statically. If you already use the latest / close to latest wasmd, you can update more or less as follows: 1. Check the current wasmd version: go list -m github.com/CosmWasm/wasmd 2. Bump the github.com/CosmWasm/wasmd dependency in your go.mod to 0.53.2 (Cosmos…

Published by the source

10 Dec 2024, 16:55 UTC

Last modified by the source

10 Dec 2024, 16:55 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vmg2-r3xv-r3xf

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

# Patch Next advisory brief: GHSA-vmg2-r3xv-r3xf

Advisory: Simulation of Wasmd message can cause crashing
IDs: GHSA-vmg2-r3xv-r3xf
Record: https://patchnext.com/advisories/ghsa-vmg2-r3xv-r3xf (revision 1, source checked 26 Oct 2026, 15:08 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: github.com/CosmWasm/wasmd 0.53.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/CosmWasm/wasmd: affected < 0.53.2; fixed in 0.53.2

## Suggested inspection (read-only)
- Go github.com/CosmWasm/wasmd: 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/CosmWasm/wasmd.
- 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-vmg2-r3xv-r3xf (GitHub-reviewed advisory GHSA-vmg2-r3xv-r3xf lists affected ranges: Go github.com/CosmWasm/wasmd >=0 <0.53.2)

Commands are suggestions: review each one before running it.