VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/tharsis/evmos: vulnerability history, versions and safety

github.com/tharsis/evmos is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Mar 2022 to Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/tharsis/evmos vulnerabilities

Vulert verdict on github.com/tharsis/evmos v1.1.3 i

Updated on 23 Oct 2026

Careful: v1.1.3 has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v1.1.3 — affected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS 7.4 i
  • With no published fix 1 i
  • Stars 1,682 i
  • Last release 51 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/tharsis/evmos, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.1.3 13 Jul 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220306144222-406d94e09f2e 06 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220306130833-21c5b48785fc 06 Mar 2022 H1 U1 Apache-2.0 No Details →
v1.1.2 06 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220306115447-e314a621b439 06 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220306072337-435f8a517a67 06 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220304175339-1bd0bf6c6476 04 Mar 2022 H1 U1 Apache-2.0 No Details →
v1.1.1 04 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220304143425-35ecc64c57ed 04 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220304125401-ea27aae6150a 04 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220303204825-98e2111f2141 03 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220303171118-8efd96b69a34 03 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220303120713-3b6c4c5e1905 03 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220303090415-8544844b79dc 03 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220303051123-5014e7778b28 03 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220302194707-4e87a598e8c2 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220302162514-a806b3f87704 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220302141613-2eb9b6386614 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220302024241-f079774ede90 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220302023323-18ab3e40c639 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v1.1.0 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220302011159-3f2c64b6a91f 02 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301234753-7de93bfb2000 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301212033-8e1823c34ee7 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301202519-2ef6ae15d7fc 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301125016-ee54f496551d 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301115227-b71526c3c8e2 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301105812-a1860c9fb13e 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220301061053-9567031762c7 01 Mar 2022 H1 U1 Apache-2.0 No Details →
v1.0.0 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228185349-d8074abc505d 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228165717-80e77fea0de8 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228154825-5d2b1498e351 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228142339-815aa5a63232 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228114352-9229b9ebc6e4 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228110344-ffefcfeed9d1 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220228101611-147341fc2e5c 28 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220227173559-57e1dc2a9f69 27 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220226222104-100d3476a2c1 26 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220226200416-0880e14e3b84 26 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220226185853-4045354d23d4 26 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220225154054-b762b13dd52f 25 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220225061426-f84240eb4b45 25 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220224153257-c2f37e7a0545 24 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220224140501-23a445a74791 24 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220224132323-66d1ec560aa2 24 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220223163333-237534998bf3 23 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220223152109-420453588ba5 23 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220218141822-82e70de2d967 18 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220217181241-42dbfde6da40 17 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220217143057-2496390b3cca 17 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220217131818-53cf5bb42895 17 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220216182525-93bb5ee6fdde 16 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220215224438-e7c88a678aee 15 Feb 2022 H1 U1 Apache-2.0 No Details →
v1.0.0-alpha1.0.20220215214622-2c0b38566058 15 Feb 2022 H1 U1 Apache-2.0 No Details →
v1.0.0-beta1 15 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220215201433-5d7b0496cb81 15 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220214225521-24265330f75d 14 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220214185326-91e117640106 14 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220214103209-47186ae9f6b8 14 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220212020726-7e03ec64a398 12 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220209192312-b59bc3f23bd3 09 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220209182235-6afdbb6bdfc4 09 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220209135151-2f9b12a9590e 09 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220208205540-1f374de1da83 08 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220208145147-c26a3ad3401c 08 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220208135424-0666892f8245 08 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220207192534-f111413ca1be 07 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220204182232-13ffafa2cf42 04 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220204103713-d892faf83e97 04 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220204094936-3fcc26e909a8 04 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220201204241-a5cef43636a0 01 Feb 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220130155048-472377ab4803 30 Jan 2022 H1 U1 Apache-2.0 No Details →
v1.0.0-alpha1 30 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220129090753-59546fdd42e5 29 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220128113901-d19726d654ef 28 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220127173600-b295aae5b85b 27 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220127063816-5da0785a2f4b 27 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220125223524-3822b39363fc 25 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220125155953-7fe9027700ac 25 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220124142145-254eb59f7ed1 24 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220121183757-e0ac095cfc0d 21 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220121023712-7e6159768254 21 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220120162005-2919c5081b19 20 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220120084737-5f1b02c1ee20 20 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220119144439-06f799968356 19 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220119112837-7fc9405bab79 19 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220119090747-ee1518dd9253 19 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220118153518-4f5a82f1ab5b 18 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220117090214-d46e9bc2ff8b 17 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220114145911-0efb5349b040 14 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220113164835-2ee7a4f18109 13 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220113151908-7d237a233c99 13 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220113135751-bfab30b0d2f3 13 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220113112937-077443f2df28 13 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220113084534-af086b34b995 13 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220113075028-405fd0627d07 13 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220112143513-baa0aeb189ca 12 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220110161703-e34c464a387a 10 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220107183539-790a73f5f055 07 Jan 2022 H1 U1 Apache-2.0 No Details →
v0.0.0-20220107141736-350a9adfb102 07 Jan 2022 H1 U1 — No Details →
v0.0.0-20220106204431-4295eb55ef77 06 Jan 2022 H1 U1 — No Details →
v0.0.0-20220106115133-a6d52d5551b2 06 Jan 2022 H1 U1 — No Details →
v0.0.0-20220105103338-14c61773352d 05 Jan 2022 H1 U1 — No Details →
v0.0.0-20220104134000-f2dec8e63a86 04 Jan 2022 H1 U1 — No Details →
v0.0.0-20220103153446-98b060db3332 03 Jan 2022 H1 U1 — No Details →
v0.0.0-20220102114500-71c4413b74ea 02 Jan 2022 H1 U1 — No Details →
v0.0.0-20220102110917-b477b28fac22 02 Jan 2022 H1 U1 — No Details →
v0.0.0-20211228171944-d8cd81f78eb8 28 Dec 2021 H1 U1 — No Details →
v0.0.0-20211216145539-4fff189b05f6 16 Dec 2021 H1 U1 — No Details →
v0.0.0-20211215184130-e54aac1a4886 15 Dec 2021 H1 U1 — No Details →
v0.0.0-20211214190542-6cae15104857 14 Dec 2021 H1 U1 — No Details →
v0.0.0-20211213235508-413ce7c995bb 13 Dec 2021 H1 U1 — No Details →
v0.0.0-20211213215111-9f3e9fd20a94 13 Dec 2021 H1 U1 — No Details →
v0.0.0-20211213160407-d16ca653ec39 13 Dec 2021 H1 U1 — No Details →
v0.0.0-20211212032217-882999dee91d 12 Dec 2021 H1 U1 — No Details →
v0.0.0-20211212005752-70e9d11f089e 12 Dec 2021 H1 U1 — No Details →
v0.4.2 11 Dec 2021 H1 U1 — No Details →
v0.0.0-20211209235550-0716a72ffd52 09 Dec 2021 H1 U1 — No Details →
v0.0.0-20211209233105-1d29bebe6a97 09 Dec 2021 H1 U1 — No Details →

The newest 120 of 199 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/tharsis/evmos

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-24738: Account compromise in Evmos 7.4 high 2.0.1 07 Mar 2022
CVE-2022-24738: Account compromise in Evmos N/A unrated No fix published 21 Aug 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/tharsis/evmos

Is github.com/tharsis/evmos safe to use?

Vulert records 2 vulnerabilities for github.com/tharsis/evmos in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/tharsis/evmos's Vulert package health score?

Vulert scores github.com/tharsis/evmos 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/tharsis/evmos affected?

Yes. v1.1.3, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does github.com/tharsis/evmos have?

2 vulnerabilities are recorded for github.com/tharsis/evmos in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/tharsis/evmos vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/tharsis/evmos in the last 12 months, and the oldest entry in this database dates to 07 Mar 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/tharsis/evmos are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/tharsis/evmos for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/tharsis/evmos version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.