Every CVESearch/Get API key

GHSA-8qxh-2gh8-r923

cheqd-node subject to Cosmos SDK "Barberry" vulnerability

No scoreFix available

GHSA-8qxh-2gh8-r923 is a vulnerability with no CVSS score yet in github.com/cheqd/cheqd-node, published June 12, 2023. No source lists public exploit code. Fixed in github.com/cheqd/cheqd-node 1.4.4.

What does this mean?
Severity
UnratedNo CVSS score yet
Exploit chance
UnscoredNo EPSS score yet
Exploitation
None knownNot on CISA’s or ENISA’s lists
Fixed in
1.4.4github.com/cheqd/cheqd-node

Description

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, the attack would be unsuccessful without a chain halt.

Workarounds

No. Node operators are recommended to upgrade to the latest release version.

References

Affected packages

Affected packages
PackageAffectedFixed
github.com/cheqd/cheqd-node
Go
before 1.4.4
1.4.4

What each source reports

GitHub AdvisoriesNo score

cheqd-node subject to Cosmos SDK "Barberry" vulnerability

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, the attack would be unsuccessful without a chain halt.

Workarounds

No. Node operators are recommended to upgrade to the latest release version.

References

Record
GHSA-8qxh-2gh8-r923
Updated
2026-11-02
OSVNo score

cheqd-node subject to Cosmos SDK "Barberry" vulnerability

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, the attack would be unsuccessful without a chain halt.

Workarounds

No. Node operators are recommended to upgrade to the latest release version.

References

Record
GHSA-8qxh-2gh8-r923
Updated
2026-11-02

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

MoveEnter Open