How severe is GHSA-33cr-m232-xqch?

No CVSS score has been assigned to GHSA-33cr-m232-xqch yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-33cr-m232-xqch?

GHSA-33cr-m232-xqch affects the following packages: github.com/cheqd/cheqd-node (Go). Ecosystems affected: Go.

How do I fix GHSA-33cr-m232-xqch?

Update github.com/cheqd/cheqd-node to 3.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33cr-m232-xqch is resolved across your whole dependency graph.

How do I detect GHSA-33cr-m232-xqch in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cheqd/cheqd-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-33cr-m232-xqch if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-33cr-m232-xqch actively exploited in the wild?

No public exploit code has been indexed for GHSA-33cr-m232-xqch yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-33cr-m232-xqch published, and has it been updated?

GHSA-33cr-m232-xqch was published on March 11, 2025 and was last updated on March 14, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

cheqd-node affected by Non-deterministic JSON Unmarshalling of IBC AcknowledgementGHSA-33cr-m232-xqch

Fix: cosmos/ibc-go@59987d5

GHSA-33cr-m232-xqch is a remote code execution vulnerability in github.com/cheqd/cheqd-node. A fix is available for github.com/cheqd/cheqd-node — see the affected versions and patch details below.

Also known asGO-2025-3514

Published

Mar 11, 2025

Updated

Mar 14, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 14, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/cheqd/cheqd-node

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in IBC-Go's deserialization of acknowledgements that results in non-deterministic behavior which can halt a chain. Any user that can open an IBC channel can introduce this state to the chain.

This an upstream dependency used in cheqd-node, rather than a custom module.

Impact

Could result in a chain halt.

Patches

Validators, full nodes, and IBC relayers should upgrade to cheqd-node v3.1.7. This upgrade does not require a software upgrade proposal on-chain and is meant to be non state-breaking.

References

See ASA-2025-004: Non-deterministic JSON Unmarshalling of IBC Acknowledgement can result in a chain halt upstream on IBC-Go.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cheqd/cheqd-node`	all versions	3.1.7`go get github.com/cheqd/cheqd-node@v3.1.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cheqd/cheqd-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cheqd/cheqd-node to 3.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33cr-m232-xqch is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

# Description [An issue was discovered in IBC-Go's deserialization of acknowledgements](https://github.com/cosmos/ibc-go/security/advisories/GHSA-jg6f-48ff-5xrw) that results in non-deterministic behavior which can halt a chain. Any user that can open an IBC channel can introduce this state to the chain. This an upstream dependency used in cheqd-node, rather than a custom module. ## Impact Could result in a chain halt. ## Patches Validators, full nodes, and IBC relayers should upgrade to **[cheqd-node v3.1.7](https://github.com/cheqd/cheqd-node/releases/tag/v3.1.7)**. This upgrade does not

O3 Security · Impact-Aware SCA

Is GHSA-33cr-m232-xqch in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

cheqd-node affected by Non-deterministic JSON Unmarshalling of IBC AcknowledgementGHSA-33cr-m232-xqch

Real-World Exposure

Description

Description

Impact

Patches

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-33cr-m232-xqch in your dependencies?