Is github.com/evmos/ethermint 0.17 vulnerable?

Go · 3 releases from 0.17.0 to 0.17.2 · latest github.com/evmos/ethermint is 0.22.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/evmos/ethermint 0.17.2, the last 0.17 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2022-35936, CVE-2022-35936. Upgrade to 0.18.0 or later to fix all of them.

Upgrade with:go get github.com/evmos/ethermint@v0.18.0

Is your project on an affected github.com/evmos/ethermint?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/evmos/ethermint 0.17.2

  • LowCVE-2022-35936GO-2022-076021 Aug 2024

    Ethermint vulnerable to DoS through unintended Contract Selfdestruct in github.com/crypto-org-chain/cronos

    Affected
    <0.18.0
    Fixed in
    0.18.0
  • HighCVE-2022-35936GHSA-f92v-grc2-w2fg18 Aug 2022

    Ethermint vulnerable to DoS through unintended Contract Selfdestruct

    Affected
    <0.18.0
    Fixed in
    0.18.0

Every github.com/evmos/ethermint 0.17.x release

Affected: 0.17.0 to 0.17.2. Latest github.com/evmos/ethermint: 0.22.0.

VersionKnown advisories
github.com/evmos/ethermint 0.17.2CVE-2022-35936, CVE-2022-35936
github.com/evmos/ethermint 0.17.1CVE-2022-35936, CVE-2022-35936
github.com/evmos/ethermint 0.17.0CVE-2022-35936, CVE-2022-35936

Which of your client projects are still on github.com/evmos/ethermint 0.17?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/evmos/ethermint version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/evmos/ethermint 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.