Cosmos packet-forward-middleware vulnerable to chain-halt
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 4.1.1; github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 6.1.1; github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 5.2.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4
- Affected
- < 4.1.1
- Fixed in
- 4.1.1
Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6
- Affected
- < 6.1.1
- Fixed in
- 6.1.1
Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5
- Affected
- < 5.2.1
- Fixed in
- 5.2.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w6rp-vxj2-fjhr lists affected ranges: Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 >=0 =0 =0 <6.1.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-w6rp-vxj2-fjhr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-w6rp-vxj2-fjhr Advisory: Cosmos packet-forward-middleware vulnerable to chain-halt IDs: GHSA-w6rp-vxj2-fjhr Record: https://patchnext.com/advisories/ghsa-w6rp-vxj2-fjhr (revision 1, source checked 26 Oct 2026, 14:59 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 4.1.1; github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 6.1.1; github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 5.2.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4: affected < 4.1.1; fixed in 4.1.1 - Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6: affected < 6.1.1; fixed in 6.1.1 - Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5: affected < 5.2.1; fixed in 5.2.1 ## Suggested inspection (read-only) - Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4: check the installed version with your package manager. - Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6: check the installed version with your package manager. - Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4, github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6, github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-w6rp-vxj2-fjhr (GitHub-reviewed advisory GHSA-w6rp-vxj2-fjhr lists affected ranges: Go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 >=0 =0 =0 <6.1.1) Commands are suggestions: review each one before running it.
Loading voting…