How severe is GHSA-m3rh-cvr5-x6q4?

GHSA-m3rh-cvr5-x6q4 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m3rh-cvr5-x6q4?

GHSA-m3rh-cvr5-x6q4 affects the following packages: github.com/CosmWasm/wasmd (Go). Ecosystems affected: Go.

How do I fix GHSA-m3rh-cvr5-x6q4?

Update github.com/CosmWasm/wasmd to 0.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3rh-cvr5-x6q4 is resolved across your whole dependency graph.

How do I detect GHSA-m3rh-cvr5-x6q4 in my Go dependencies?

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.

How do I mitigate GHSA-m3rh-cvr5-x6q4 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-m3rh-cvr5-x6q4?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m3rh-cvr5-x6q4 can be triaged on real exposure rather than presence alone.

Is GHSA-m3rh-cvr5-x6q4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m3rh-cvr5-x6q4 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-m3rh-cvr5-x6q4 published, and has it been updated?

GHSA-m3rh-cvr5-x6q4 was published on August 8, 2024 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

LOW severity

GHSA-m3rh-cvr5-x6q4 — wasmd

LOWFix: CosmWasm/wasmd@76c0c06

GHSA-m3rh-cvr5-x6q4 is a low-severity (CVSS 3.7) vulnerability in github.com/CosmWasm/wasmd. A fix is available for github.com/CosmWasm/wasmd — see the affected versions and patch details below.

CosmWasm wasmd has large address count in ValidateBasic

Also known asGO-2024-3059

Published

Aug 8, 2024

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 6, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/CosmWasm/wasmd

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/CosmWasm/wasmd`	all versions	0.52.0`go get github.com/CosmWasm/wasmd@v0.52.0`

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/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.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3rh-cvr5-x6q4 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-m3rh-cvr5-x6q4 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m3rh-cvr5-x6q4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Component:** wasmd **Criticality:** Low ([ACMv1](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md): 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](https://github.com/CosmWasm/advisories/blob/main/CWAs/CWA-2024-003.md) for more details.

O3 Security · Impact-Aware SCA

Is GHSA-m3rh-cvr5-x6q4 in your dependencies?

O3 Security finds GHSA-m3rh-cvr5-x6q4 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works