GHSA-w6rp-vxj2-fjhr
Cosmos packet-forward-middleware vulnerable to chain-halt
Blast Radius
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/v6Real-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 | all versions | 4.1.1 |
| 🐹Go | github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 | all versions | 5.2.1 |
| 🐹Go | github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 | all versions | 6.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-w6rp-vxj2-fjhr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w6rp-vxj2-fjhr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w6rp-vxj2-fjhr in your dependencies?
O3 detects GHSA-w6rp-vxj2-fjhr across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.