cheqd-node subject to Cosmos SDK "Barberry" vulnerability

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 dubbed "Barberry" affects the Cosmos SDK framework used by cheqd-node as base. It impacts the way Cosmos SDK handles vesting accounts, and can therefore be a high-impact vulnerability for any network running the framework. There is no vulnerability in the DID/resource modules for cheqd-node. Patches Node operators are requested to upgrade to cheqd-node v1.4.4. This is not a state-breaking release and does not require a coordinated upgrade across all node operators. This vulnerability was patched in Cosmos SDK v0.46.13. Since this version switches to Go v1.19 and also changes the namespace of many Cosmos protobuf packages, the Barberry fix was backported to cheqd's fork of Cosmos SDK. Mitigation When at least ~33% of the voting power of the network has deployed the recommended version of the software, any attack would be unsuccessful but cause a chain halt. Once at least ~67% of the voting power of the network has deployed recommended version of the software,…

Published by the source

12 Jun 2023, 18:34 UTC

Last modified by the source

12 Jun 2023, 18:34 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8qxh-2gh8-r923

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

# Patch Next advisory brief: GHSA-8qxh-2gh8-r923

Advisory: cheqd-node subject to Cosmos SDK "Barberry" vulnerability
IDs: GHSA-8qxh-2gh8-r923
Record: https://patchnext.com/advisories/ghsa-8qxh-2gh8-r923 (revision 1, source checked 26 Oct 2026, 14:58 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 1.4.4. A vendor fix does not mean a deployment is fixed.

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

## 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-8qxh-2gh8-r923 (GitHub-reviewed advisory GHSA-8qxh-2gh8-r923 lists affected ranges: Go github.com/cheqd/cheqd-node >=0 <1.4.4)

Commands are suggestions: review each one before running it.