What is GHSA-79XG-Q4QM-7V9W?

GHSA-79XG-Q4QM-7V9W is a high-severity security vulnerability in github.com/CosmWasm/wasmd (go), affecting versions = 0.60.0. It is fixed in 0.60.1, 0.55.1, 0.54.1, 0.53.3.

Which versions of github.com/CosmWasm/wasmd are affected by GHSA-79XG-Q4QM-7V9W?

github.com/CosmWasm/wasmd (go) versions = 0.60.0 is affected.

Is there a fix for GHSA-79XG-Q4QM-7V9W?

Yes. GHSA-79XG-Q4QM-7V9W is fixed in 0.60.1, 0.55.1, 0.54.1, 0.53.3. Upgrade to this version or later.

Is GHSA-79XG-Q4QM-7V9W exploitable, and should I be worried?

Whether GHSA-79XG-Q4QM-7V9W 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-79XG-Q4QM-7V9W 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-79XG-Q4QM-7V9W in github.com/CosmWasm/wasmd

Q: How do I fix GHSA-79XG-Q4QM-7V9W?

Upgrade: github.com/CosmWasm/wasmd to 0.60.1 or later, github.com/CosmWasm/wasmd to 0.55.1 or later, github.com/CosmWasm/wasmd to 0.54.1 or later, github.com/CosmWasm/wasmd to 0.53.3 or later.

Summary

CWA-2025-006: wasmd's improper error handling may lead to IBC channel opening despite error

CWA-2025-006: Improper error handling may lead to IBC channel opening despite error

Severity

High (Considerable + Likely)[^1]

Affected versions:

wasmd 0.60.0
wasmd >= 0.51.0 < 0.55.1

Patched versions:

wasmd 0.60.1, 0.55.1, 0.54.1, 0.53.3

Description of the bug

A contract erroring during IBC channel opening does not prevent the channel from opening.

Applying the patch

The patch will be shipped in a wasmd release. You will also have to update libwasmvm if you build statically.
If you already use the latest / close to latest wasmd, you can update more or less as follows:

Check the current wasmd version: go list -m github.com/CosmWasm/wasmd
Bump the github.com/CosmWasm/wasmd dependency in your go.mod to 0.60.1 (Cosmos SDK 0.53 compatible), 0.55.1 (Cosmos SDK 0.50 compatible), 0.54.1 or 0.53.3; go mod tidy; commit.
If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, make sure that you use the same version as your wasmvm version.
Check the updated wasmd version: go list -m github.com/CosmWasm/wasmd and ensure you see 0.60.1, 0.55.1, 0.54.1 or 0.53.3.
Follow your regular practices to deploy chain upgrades.

The patch is consensus breaking.

Acknowledgement

This problem was discovered during an audit of the CosmWasm stack performed by Sherlock and funded by ICF/ICL in Q1 2025. Thank you for that work!

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

2025-03-03: Auditor informs Confio about this issue.
2025-04-10: Confio developed the patch internally.
2025-06-05: Upcoming patch is announced.
2025-06-10: Patch is released.

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

Impact

Affected versions

github.com/CosmWasm/wasmd (= 0.60.0) github.com/CosmWasm/wasmd (>= 0.55.0, < 0.55.1) github.com/CosmWasm/wasmd (>= 0.54.0, < 0.54.1) github.com/CosmWasm/wasmd (>= 0.51.0, < 0.53.3)

Security releases

github.com/CosmWasm/wasmd → 0.60.1 (go) github.com/CosmWasm/wasmd → 0.55.1 (go) github.com/CosmWasm/wasmd → 0.54.1 (go) github.com/CosmWasm/wasmd → 0.53.3 (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 the following packages to resolve this vulnerability:

github.com/CosmWasm/wasmd to 0.60.1 or later; github.com/CosmWasm/wasmd to 0.55.1 or later; github.com/CosmWasm/wasmd to 0.54.1 or later; github.com/CosmWasm/wasmd to 0.53.3 or later

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

Frequently Asked Questions

What is GHSA-79XG-Q4QM-7V9W? GHSA-79XG-Q4QM-7V9W is a high-severity security vulnerability in github.com/CosmWasm/wasmd (go), affecting versions = 0.60.0. It is fixed in 0.60.1, 0.55.1, 0.54.1, 0.53.3.
Which versions of github.com/CosmWasm/wasmd are affected by GHSA-79XG-Q4QM-7V9W? github.com/CosmWasm/wasmd (go) versions = 0.60.0 is affected.
Is there a fix for GHSA-79XG-Q4QM-7V9W? Yes. GHSA-79XG-Q4QM-7V9W is fixed in 0.60.1, 0.55.1, 0.54.1, 0.53.3. Upgrade to this version or later.
Is GHSA-79XG-Q4QM-7V9W exploitable, and should I be worried? Whether GHSA-79XG-Q4QM-7V9W 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-79XG-Q4QM-7V9W 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-79XG-Q4QM-7V9W?
- Upgrade github.com/CosmWasm/wasmd to 0.60.1 or later
- Upgrade github.com/CosmWasm/wasmd to 0.55.1 or later
- Upgrade github.com/CosmWasm/wasmd to 0.54.1 or later
- Upgrade github.com/CosmWasm/wasmd to 0.53.3 or later

Other vulnerabilities in github.com/CosmWasm/wasmd

CVE-IDSeverityPackage summary

GHSA-VMG2-R3XV-R3XFLowgithub.com/CosmWasm/wasmd: Simulation of Wasmd message can cause crashing GHSA-FPGJ-CR28-FVPXMediumgithub.com/CosmWasm/wasmd: CWA-2024-006: wasmd non-deterministic module_query_safe query GHSA-G8W7-7VGG-X7XGHighgithub.com/CosmWasm/wasmd: CWA-2024-005: Stackoverflow in wasmd GHSA-M3RH-CVR5-X6Q4Mediumgithub.com/CosmWasm/wasmd: CosmWasm wasmd has large address count in ValidateBasic