What is GHSA-M3RH-CVR5-X6Q4?

GHSA-M3RH-CVR5-X6Q4 is a medium-severity uncontrolled resource consumption vulnerability in github.com/CosmWasm/wasmd (go), affecting versions < 0.52.0. It is fixed in 0.52.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-M3RH-CVR5-X6Q4?

GHSA-M3RH-CVR5-X6Q4 has a CVSS score of 3.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/CosmWasm/wasmd are affected by GHSA-M3RH-CVR5-X6Q4?

github.com/CosmWasm/wasmd (go) versions < 0.52.0 is affected.

Is there a fix for GHSA-M3RH-CVR5-X6Q4?

Yes. GHSA-M3RH-CVR5-X6Q4 is fixed in 0.52.0. Upgrade to this version or later.

Is GHSA-M3RH-CVR5-X6Q4 exploitable, and should I be worried?

Whether GHSA-M3RH-CVR5-X6Q4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-M3RH-CVR5-X6Q4 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-M3RH-CVR5-X6Q4 in github.com/CosmWasm/wasmd

Q: How severe is GHSA-M3RH-CVR5-X6Q4?

GHSA-M3RH-CVR5-X6Q4 has a CVSS score of 3.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/CosmWasm/wasmd are affected by GHSA-M3RH-CVR5-X6Q4?

github.com/CosmWasm/wasmd (go) versions < 0.52.0 is affected.

Q: Is there a fix for GHSA-M3RH-CVR5-X6Q4?

Yes. GHSA-M3RH-CVR5-X6Q4 is fixed in 0.52.0. Upgrade to this version or later.

Q: Is GHSA-M3RH-CVR5-X6Q4 exploitable, and should I be worried?

Whether GHSA-M3RH-CVR5-X6Q4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-M3RH-CVR5-X6Q4 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-M3RH-CVR5-X6Q4?

Upgrade github.com/CosmWasm/wasmd to 0.52.0 or later.

Summary

CosmWasm wasmd has large address count in ValidateBasic

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.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-M3RH-CVR5-X6Q4 has a CVSS score of 3.7 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.52.0); upgrading removes the vulnerable code path.

Affected versions

github.com/CosmWasm/wasmd (< 0.52.0)

Security releases

github.com/CosmWasm/wasmd → 0.52.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/CosmWasm/wasmd to 0.52.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-M3RH-CVR5-X6Q4? GHSA-M3RH-CVR5-X6Q4 is a medium-severity uncontrolled resource consumption vulnerability in github.com/CosmWasm/wasmd (go), affecting versions < 0.52.0. It is fixed in 0.52.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-M3RH-CVR5-X6Q4? GHSA-M3RH-CVR5-X6Q4 has a CVSS score of 3.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/CosmWasm/wasmd are affected by GHSA-M3RH-CVR5-X6Q4? github.com/CosmWasm/wasmd (go) versions < 0.52.0 is affected.
Is there a fix for GHSA-M3RH-CVR5-X6Q4? Yes. GHSA-M3RH-CVR5-X6Q4 is fixed in 0.52.0. Upgrade to this version or later.
Is GHSA-M3RH-CVR5-X6Q4 exploitable, and should I be worried? Whether GHSA-M3RH-CVR5-X6Q4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-M3RH-CVR5-X6Q4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-M3RH-CVR5-X6Q4? Upgrade github.com/CosmWasm/wasmd to 0.52.0 or later.