Skip to content
Fencer Intel
medium —

GHSA-6fgm-x6ff-w78f json

Potential Denial-of-Service condition leading to temporary disability in IBC transfers to the native chain

published last yr. modified 8mo ago also GO-2025-3463

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

Chains using affected versions of Packet Forward Middleware in their IBC Transfer stack are vulnerable to an attack in which there is a potential denial of service. This affects IBC transfers for any asset which is being transferred between another chain and its native chain.

We recommend upgrading as soon as possible.

__THIS IS A STATE BREAKING CHANGE__

### Patches Versions [7.2.1](https://github.com/cosmos/ibc-apps/releases/tag/middleware%2Fpacket-forward-middleware%2Fv7.2.1) and [8.1.1](https://github.com/cosmos/ibc-apps/releases/tag/middleware%2Fpacket-forward-middleware%2Fv8.1.1) are patched.

### Workarounds N/A

### References N/A

Patch / fix

  • go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v7 7.2.1
  • go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v8 8.1.1

Is GHSA-6fgm-x6ff-w78f in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v7
<7.2.1
7.2.1
go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v8
<8.1.1
8.1.1
go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4
all versions
 no fix listed
go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5
all versions
 no fix listed
go github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6
all versions
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.