Yes. github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 (Go): upgrade to 4.1.1 or later; github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 (Go): upgrade to 5.2.1 or later; github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 (Go): upgrade to 6.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected?
Check whether you run github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 (Go), github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 (Go) or github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4 (Go): upgrade to 4.1.1 or later
go get github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v4@v4.1.1
github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5 (Go): upgrade to 5.2.1 or later
go get github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v5@v5.2.1
github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6 (Go): upgrade to 6.1.1 or later
go get github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v6@v6.1.1