Is github.com/tharsis/evmos/v2 2.0 vulnerable?
Go · 3 releases from 2.0.0 to 2.0.2 · latest github.com/tharsis/evmos/v2 is 2.0.2 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. github.com/tharsis/evmos/v2 2.0.2, the last 2.0 release, is affected by 2 known security advisories (1 critical, 1 low), including CVE-2024-32644, CVE-2024-32644. 1 more affects earlier 2.0.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/tharsis/evmos/v2?
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/v2 2.0.2
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
- <=2.0.2
- Fixed in
- No fix released
Fixed within 2.0.x, affecting earlier releases
Account compromise in Evmos in github.com/tharsis/evmos
- Affected
- <2.0.1
- Fixed in
- 2.0.1
Every github.com/tharsis/evmos/v2 2.0.x release
Affected: 2.0.0 to 2.0.2.
| Version | Known advisories |
|---|---|
| github.com/tharsis/evmos/v2 2.0.2 | CVE-2024-32644, CVE-2024-32644 |
| github.com/tharsis/evmos/v2 2.0.1 | CVE-2024-32644, CVE-2024-32644 |
| github.com/tharsis/evmos/v2 2.0.0 | CVE-2022-24738, CVE-2024-32644, CVE-2024-32644 |
Which of your client projects are still on github.com/tharsis/evmos/v2 2.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/tharsis/evmos/v2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
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.