Is github.com/tharsis/evmos 0.3 vulnerable?
Go · 1 release from 0.3.0 to 0.3.0 · latest github.com/tharsis/evmos is 1.1.3 · checked 18 Nov 2026
Yes: 5 known advisories
Yes. github.com/tharsis/evmos 0.3.0, the last 0.3 release, is affected by 5 known security advisories (1 critical, 2 high, 2 low), including CVE-2024-32644, CVE-2022-24738, CVE-2021-43839. At least one has no fixed release yet.
Is your project on an affected github.com/tharsis/evmos?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/tharsis/evmos 0.3.0
Account compromise in Evmos in github.com/tharsis/evmos
- Affected
- All versions
- Fixed in
- No fix released
Evmos transaction execution not accounting for all state transition after interaction with precompiles in github.com/evmos/evmos
- Affected
- All versions
- Fixed in
- No fix released
Evmos transaction execution not accounting for all state transition after interaction with precompiles
- Affected
- <=1.1.3
- Fixed in
- No fix released
Account compromise in Evmos
- Affected
- <2.0.1
- Fixed in
- 2.0.1
Drainage of FeeCollector's Block Transaction Fees in cronos
- Affected
- <=0.4.2
- Fixed in
- No fix released
Which of your client projects are still on github.com/tharsis/evmos 0.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/tharsis/evmos version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/tharsis/evmos 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.