How severe is GHSA-23qp-3c2m-xx6w?

No CVSS score has been assigned to GHSA-23qp-3c2m-xx6w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-23qp-3c2m-xx6w?

GHSA-23qp-3c2m-xx6w affects the following packages: github.com/CosmWasm/wasmvm (Go), github.com/CosmWasm/wasmvm/v2 (Go), github.com/CosmWasm/wasmvm/v2 (Go), github.com/CosmWasm/wasmvm/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-23qp-3c2m-xx6w?

Update github.com/CosmWasm/wasmvm to 1.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23qp-3c2m-xx6w is resolved across your whole dependency graph.

How do I detect GHSA-23qp-3c2m-xx6w in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/CosmWasm/wasmvm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-23qp-3c2m-xx6w if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-23qp-3c2m-xx6w?

O3 pinpoints whether GHSA-23qp-3c2m-xx6w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-23qp-3c2m-xx6w actively exploited in the wild?

No public exploit code has been indexed for GHSA-23qp-3c2m-xx6w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-23qp-3c2m-xx6w published, and has it been updated?

GHSA-23qp-3c2m-xx6w was published on February 4, 2025 and was last updated on February 6, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-23qp-3c2m-xx6w: wasmvm: Malicious smart contract can crash…

Blast Radius

4 pkgs affected

🐹github.com/CosmWasm/wasmvm🐹github.com/CosmWasm/wasmvm/v2🐹github.com/CosmWasm/wasmvm/v2🐹github.com/CosmWasm/wasmvm/v2

Real-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

CWA-2025-001

Severity

Medium (Moderate + Likely)¹

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 crash the chain. The underlying bug that causes this is present on both permissioned and premissionless chains, but it can only be triggered reliably with a malicious contract, so permissioned chains are much less likely to be affected.

(We'll add more detail once chains had a chance to upgrade.)

Patch

Applying the patch

The patch will be shipped in releases of wasmvm. You can update more or less as follows:

Check the current wasmvm version: go list -m github.com/CosmWasm/wasmvm
Bump the github.com/CosmWasm/wasmvm dependency in your go.mod to one of the patched version depending on which minor version you are on; go mod tidy; commit.
If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, update them accordingly.
Check the updated wasmvm version: go list -m github.com/CosmWasm/wasmvm and ensure you see 1.5.8, 2.0.6, 2.1.5 or 2.2.2.
Follow your regular practices to deploy chain upgrades.

While the fix for this issue is not consensus breaking, the patch contains another consensus breaking fix and requires a coordinated upgrade.

Acknowledgement

This issue was found by meadow101 who reported it to the Cosmos Bug Bounty Program on HackerOne.

If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see https://hackerone.com/cosmos.

Timeline

2024-11-25: Confio receives a report through the Cosmos bug bounty program maintained by Amulet.
2024-11-28: Confio security contributors confirm the report.
2024-11-28: Confio developed the patch internally.
2025-02-04: Patch gets released.

Footnotes

following Amulet's Severity Classification Framework ACMv1.2: https://github.com/interchainio/security/blob/0295254e8645301ccb606d46108a45cede0a73e0/resources/CLASSIFICATION_MATRIX.md ↩

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/CosmWasm/wasmvm`	all versions	1.5.8
🐹Go	`github.com/CosmWasm/wasmvm/v2`	≥ 2.0.0&&< 2.0.6	2.0.6
🐹Go	`github.com/CosmWasm/wasmvm/v2`	≥ 2.1.0&&< 2.1.5	2.1.5
🐹Go	`github.com/CosmWasm/wasmvm/v2`	≥ 2.2.0&&< 2.2.2	2.2.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/CosmWasm/wasmvm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/CosmWasm/wasmvm to 1.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23qp-3c2m-xx6w 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.
How O3 protects you
O3 pinpoints whether GHSA-23qp-3c2m-xx6w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-23qp-3c2m-xx6w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# CWA-2025-001 **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 crash the chain. The underlying bug that causes this is present on both permissioned and premissionless chains, but it can only be triggered _reliably_ with a malicious contract, so permissioned chains are much less likely to be affected. (We'll add more detail once chains had a chance to upgr

O3 Security · Impact-Aware SCA

Is GHSA-23qp-3c2m-xx6w in your dependencies?

O3 detects GHSA-23qp-3c2m-xx6w across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-23qp-3c2m-xx6w