CWA-2024-006: wasmd non-deterministic module_query_safe queryGHSA-fpgj-cr28-fvpx
Fix: CosmWasm/wasmd@db8981dGHSA-fpgj-cr28-fvpx is a security vulnerability in github.com/CosmWasm/wasmd. A fix is available for github.com/CosmWasm/wasmd — see the affected versions and patch details below.
Real-World Exposure
github.com/CosmWasm/wasmdReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Component: wasmd Criticality: Medium (ACMv1: I:Moderate; L:Likely) Patched versions: wasmd 0.53.0
See CWA-2024-006 for more details.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/CosmWasm/wasmd | ≥ 0.52.0&&< 0.53.0 | 0.53.0go get github.com/CosmWasm/wasmd@v0.53.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/CosmWasm/wasmd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/CosmWasm/wasmd to 0.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpgj-cr28-fvpx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-fpgj-cr28-fvpx in your dependencies?
Find it across Go, including transitive dependencies.