Potential inter-blockchain communication (IBC) protocol compromise via "Dragonberry" vulnerability in cheqd

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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. Patches 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. 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 - IBC Security Advisory on "Dragonberry" (and associated security vulnerability "Dragonfruit") For more information If you have any questions or comments about this advisory: Open an issue in cheqd-node repo Email us at…

Published by the source

18 Oct 2022, 17:27 UTC

Last modified by the source

7 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j92c-mmf7-j5x5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-j92c-mmf7-j5x5

Advisory: Potential inter-blockchain communication (IBC) protocol compromise via "Dragonberry" vulnerability in cheqd
IDs: GHSA-j92c-mmf7-j5x5
Record: https://patchnext.com/advisories/ghsa-j92c-mmf7-j5x5 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cheqd/cheqd-node 0.6.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cheqd/cheqd-node: affected < 0.6.9; fixed in 0.6.9

## Suggested inspection (read-only)
- Go github.com/cheqd/cheqd-node: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cheqd/cheqd-node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j92c-mmf7-j5x5 (GitHub-reviewed advisory GHSA-j92c-mmf7-j5x5 lists affected ranges: Go github.com/cheqd/cheqd-node >=0 <0.6.9)

Commands are suggestions: review each one before running it.