Summary
Potential inter-blockchain communication (IBC) protocol compromise via "Dragonberry" vulnerability in cheqd
Workarounds
No. The patch takes effect when more than 2/3rds of the voting power of the cheqd network has upgraded to this patch.
An emergency hotfix was released previously under v0.6.8 but this is now deprecated since Cosmos SDK v0.45.9 officially fixes this upstream.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in cheqd-node repo
- Email us at [email protected]
- Message us on our community Slack or Discord
Impact
This vulnerability affects IBC transfers due to a security vulnerability dubbed "Dragonberry" upstream in Cosmos SDK. The vulnerability could allow malicious attackers to compromise chain-to-chain IBC transfers.
There is no vulnerability in the DID/resource modules for cheqd-node.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
Node operators are requested to upgrade to cheqd-node v0.6.9 as soon as possible. Installation instructions are in the release notes. Please do not install any beta/pre-release versions.
Frequently Asked Questions
- What is GHSA-J92C-MMF7-J5X5? GHSA-J92C-MMF7-J5X5 is a high-severity security vulnerability in github.com/cheqd/cheqd-node (go), affecting versions < 0.6.9. It is fixed in 0.6.9.
- Which versions of github.com/cheqd/cheqd-node are affected by GHSA-J92C-MMF7-J5X5? github.com/cheqd/cheqd-node (go) versions < 0.6.9 is affected.
- Is there a fix for GHSA-J92C-MMF7-J5X5? Yes. GHSA-J92C-MMF7-J5X5 is fixed in 0.6.9. Upgrade to this version or later.
- Is GHSA-J92C-MMF7-J5X5 exploitable, and should I be worried? Whether GHSA-J92C-MMF7-J5X5 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-J92C-MMF7-J5X5 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-J92C-MMF7-J5X5? Upgrade
github.com/cheqd/cheqd-nodeto 0.6.9 or later.