Is cosmossdk.io/x/tx 0.2 vulnerable?
Go · 3 releases from 0.2.0 to 0.2.2 · latest cosmossdk.io/x/tx is 1.1.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. cosmossdk.io/x/tx 0.2.2, the last 0.2 release, is affected by 2 known security advisories (1 high, 1 low). Upgrade to 0.13.7 or later to fix all of them.
go get cosmossdk.io/x/tx@v0.13.7Is your project on an affected cosmossdk.io/x/tx?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting cosmossdk.io/x/tx 0.2.2
Transaction decoding may result in a stack overflow or resource exhaustion in github.com/cosmos/cosmos-sdk
- Affected
- <0.13.7
- Fixed in
- 0.13.7
ASA-2024-0012, ASA-2024-0013: CosmosSDK: Transaction decoding may result in a stack overflow or resource exhaustion
- Affected
- <0.13.7
- Fixed in
- 0.13.7
Every cosmossdk.io/x/tx 0.2.x release
Affected: 0.2.0 to 0.2.2. Latest cosmossdk.io/x/tx: 1.1.0.
| Version | Known advisories |
|---|---|
| cosmossdk.io/x/tx 0.2.2 | GO-2024-3339, GHSA-8wcc-m6j2-qxvm |
| cosmossdk.io/x/tx 0.2.1 | GO-2024-3339, GHSA-8wcc-m6j2-qxvm |
| cosmossdk.io/x/tx 0.2.0 | GO-2024-3339, GHSA-8wcc-m6j2-qxvm |
Which of your client projects are still on cosmossdk.io/x/tx 0.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact cosmossdk.io/x/tx version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other cosmossdk.io/x/tx versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.