How severe is GHSA-w6rp-vxj2-fjhr?

No CVSS score has been assigned to GHSA-w6rp-vxj2-fjhr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w6rp-vxj2-fjhr?

GHSA-w6rp-vxj2-fjhr affects the following packages: github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 (Go), github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 (Go), github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 (Go). Ecosystems affected: Go.

How do I fix GHSA-w6rp-vxj2-fjhr?

Update github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w6rp-vxj2-fjhr is resolved across your whole dependency graph.

How do I mitigate GHSA-w6rp-vxj2-fjhr 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-w6rp-vxj2-fjhr actively exploited in the wild?

No public exploit code has been indexed for GHSA-w6rp-vxj2-fjhr 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-w6rp-vxj2-fjhr published, and has it been updated?

GHSA-w6rp-vxj2-fjhr was published on October 26, 2023 and was last updated on August 21, 2024. 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

Cosmos packet-forward-middleware vulnerable to chain-haltGHSA-w6rp-vxj2-fjhr

GHSA-w6rp-vxj2-fjhr is a security vulnerability in github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4. A fix is available for github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 — see the affected versions and patch details below.

Also known asGO-2023-2156

Published

Oct 26, 2023

Updated

Aug 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

🐹github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4🐹github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5🐹github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6

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

The Cosmos SDK is used for Inter-Blockchain Communication Protocol (IBC) applications and middleware. The packet-forward-middleware module is an IBC middleware module built for Cosmos blockchains utilizing the IBC protocol allowing routing of incoming IBC packets from a source chain to a destination chain. The packet-forward-middleware module is vulnerable to potential chain-halt due to error non-determinism.

Patches

Please patch at your earliest convenience by applying one of the following patch versions, respective to the chain's ibc-go major version: v4.1.1 v5.2.1 v6.1.1

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4`	all versions	4.1.1`go get github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4@v4.1.1`
🐹Go	`github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5`	all versions	5.2.1`go get github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5@v5.2.1`
🐹Go	`github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6`	all versions	6.1.1`go get github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6@v6.1.1`

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/cosmos/ibc-apps/middleware/packet-forward-middleware/v4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 to 4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w6rp-vxj2-fjhr 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

The Cosmos SDK is used for Inter-Blockchain Communication Protocol (IBC) applications and middleware. The [packet-forward-middleware](https://github.com/cosmos/ibc-apps/tree/main/middleware/packet-forward-middleware) module is an IBC middleware module built for Cosmos blockchains utilizing the IBC protocol allowing routing of incoming IBC packets from a source chain to a destination chain. The `packet-forward-middleware` module is vulnerable to potential chain-halt due to error non-determinism. ### Patches Please patch at your earliest convenience by applying one of the following patch versio

O3 Security · Impact-Aware SCA

Is GHSA-w6rp-vxj2-fjhr in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works