How severe is GHSA-h2rp-8vpx-q9r4?

No CVSS score has been assigned to GHSA-h2rp-8vpx-q9r4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h2rp-8vpx-q9r4?

GHSA-h2rp-8vpx-q9r4 affects the following packages: github.com/cheqd/cheqd-node (Go). Ecosystems affected: Go.

How do I fix GHSA-h2rp-8vpx-q9r4?

Update github.com/cheqd/cheqd-node to 3.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h2rp-8vpx-q9r4 is resolved across your whole dependency graph.

How do I detect GHSA-h2rp-8vpx-q9r4 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-h2rp-8vpx-q9r4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-h2rp-8vpx-q9r4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h2rp-8vpx-q9r4 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-h2rp-8vpx-q9r4 published, and has it been updated?

GHSA-h2rp-8vpx-q9r4 was published on March 13, 2025 and was last updated on March 25, 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 Security patch for upstream vulnerabilities in IBC-Go (ISA-2025-001) and Cosmos SDK (ISA-2025-002)GHSA-h2rp-8vpx-q9r4

Fix: cheqd/cheqd-node@5a58b08

GHSA-h2rp-8vpx-q9r4 is a security 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-3520

Published

Mar 13, 2025

Updated

Mar 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 25, 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

There have been two upstream security advisories and associated patches published under ISA-2025-001 and ISA-2025-002.

ISA-2025-001 affects the IBC-Go package., where non-deterministic JSON unmarshalling of IBC Acknowledgements can result in a chain halt.

ISA-2025-002 affects the Cosmos SDK package, where x/group can halt when erroring in EndBlocker.

Impact

If unaddressed, this could result in a chain halt.

Patches

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

Affected Packages

1 total 1 fixed

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

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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h2rp-8vpx-q9r4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

# Description There have been two upstream security advisories and associated patches published under [ISA-2025-001](https://github.com/cosmos/ibc-go/security/advisories/GHSA-4wf3-5qj9-368v) and [ISA-2025-002](https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-47ww-ff84-4jrg). **[ISA-2025-001](https://github.com/cosmos/ibc-go/security/advisories/GHSA-4wf3-5qj9-368v)** affects the IBC-Go package., where non-deterministic JSON unmarshalling of IBC Acknowledgements can result in a chain halt. **[ISA-2025-002](https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-47ww-ff84-4

O3 Security · Impact-Aware SCA

Is GHSA-h2rp-8vpx-q9r4 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

cheqd-node Security patch for upstream vulnerabilities in IBC-Go (ISA-2025-001) and Cosmos SDK (ISA-2025-002)GHSA-h2rp-8vpx-q9r4

Real-World Exposure

Description

Description

Impact

Patches

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-h2rp-8vpx-q9r4 in your dependencies?