CosmWasm wasmd has large address count in ValidateBasic
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/CosmWasm/wasmd 0.52.0), 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
- Affected
- < 0.52.0
- Fixed in
- 0.52.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-m3rh-cvr5-x6q4 lists affected ranges: Go github.com/CosmWasm/wasmd >=0 <0.52.0
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
- 6.3 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/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: wasmd Criticality: Low (ACMv1: I:Moderate; L:Unlikely) Patched versions: wasmd 0.52.0 In multiple wasmd message types it was possible to add a large number of addresses which might lead to unexpected resource consumption in ValidateBasic. See CWA-2024-003 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-m3rh-cvr5-x6q4
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-m3rh-cvr5-x6q4 Advisory: CosmWasm wasmd has large address count in ValidateBasic IDs: GHSA-m3rh-cvr5-x6q4 Record: https://patchnext.com/advisories/ghsa-m3rh-cvr5-x6q4 (revision 1, source checked 26 Oct 2026, 15:24 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.3) 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.52.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/CosmWasm/wasmd: affected < 0.52.0; fixed in 0.52.0 ## 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-m3rh-cvr5-x6q4 (GitHub-reviewed advisory GHSA-m3rh-cvr5-x6q4 lists affected ranges: Go github.com/CosmWasm/wasmd >=0 <0.52.0) Commands are suggestions: review each one before running it.
Loading voting…