GHSA-75qh-gg76-p2w4 — cosmwasm-vm
MEDIUMGHSA-75qh-gg76-p2w4 is a medium-severity (CVSS 5.3) vulnerability in cosmwasm-vm. A fix is available for cosmwasm-vm — see the affected versions and patch details below.
CWA-2023-004: Excessive number of function parameters in compiled Wasm
Real-World Exposure
cosmwasm-vm🦀cosmwasm-vm🦀cosmwasm-vm🦀cosmwasm-vm🐹github.com/CosmWasm/wasmvm🐹github.com/CosmWasm/wasmvm🐹github.com/CosmWasm/wasmvm🐹github.com/CosmWasm/wasmvmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
A specifically crafted Wasm file can cause the VM to consume excessive amounts of memory when compiling a contract. This can lead to high memory usage, slowdowns, potentially a crash and can poison a lock in the VM, preventing any further interaction with contracts.
For more information, see CWA-2023-004.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | cosmwasm-vm | all versions | 1.2.8cargo update -p cosmwasm-vm --precise 1.2.8 |
| 🦀crates.io | cosmwasm-vm | ≥ 1.3.0&&< 1.3.4 | 1.3.4cargo update -p cosmwasm-vm --precise 1.3.4 |
| 🦀crates.io | cosmwasm-vm | ≥ 1.4.0&&< 1.4.2 | 1.4.2cargo update -p cosmwasm-vm --precise 1.4.2 |
| 🦀crates.io | cosmwasm-vm | ≥ 1.5.0&&< 1.5.1 | 1.5.1cargo update -p cosmwasm-vm --precise 1.5.1 |
| 🐹Go | github.com/CosmWasm/wasmvm | all versions | 1.2.5go get github.com/CosmWasm/wasmvm@v1.2.5 |
| 🐹Go | github.com/CosmWasm/wasmvm | ≥ 1.3.0&&< 1.3.1 | 1.3.1go get github.com/CosmWasm/wasmvm@v1.3.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cosmwasm-vm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cosmwasm-vm to 1.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-75qh-gg76-p2w4 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-75qh-gg76-p2w4 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-75qh-gg76-p2w4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-75qh-gg76-p2w4 in your dependencies?
O3 Security finds GHSA-75qh-gg76-p2w4 across crates.io, Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.