VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cosmos/interchain-security/v5: vulnerability history, versions and safety

github.com/cosmos/interchain-security/v5 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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/cosmos/interchain-security/v5 vulnerabilities

Vulert verdict on github.com/cosmos/interchain-security/v5 v5.2.0 i

Updated on 23 Oct 2026

Good news: v5.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 76/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

What to do: Stay on v5.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v5.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v5.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Sep 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 194 i
  • Last release 25 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/cosmos/interchain-security/v5, 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
v5.0.0-20240905162918-300530f18130 05 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240905110833-29ad7145914f 05 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240904161413-954f77c8c6f2 04 Sep 2024 none Apache-2.0 — Details →
v5.2.0 04 Sep 2024 none Apache-2.0 — Details →
v5.1.2-0.20240904133759-1dd38851dbb9 04 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240904123237-ac22ba37313c 04 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240904071545-7301916eeafa 04 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240903195423-6b148c74e014 03 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240903150431-38320a2333c6 03 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240903101737-5f1a27cf0307 03 Sep 2024 none Apache-2.0 — Details →
v5.0.0-20240830143040-6262e42539b0 30 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240829173446-4c30f6bef967 29 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240829091139-29b1bf4d6940 29 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240829085830-43ecf100aa0e 29 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240829084649-7aa6db910325 29 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240829074417-0e9d9f4abb93 29 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240828175130-289e05c77c88 28 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240828132703-cc68344cd0f1 28 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240827183933-771be378b7b7 27 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240827132503-3b717d207962 27 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240827110429-0fc69685c98d 27 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240823161435-40eb3fde9a84 23 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240823135732-3a0c55f65769 23 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240806104629-29327696b8e6 06 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240802132146-2042c82ce19a 02 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240802125602-fa1e09444aae 02 Aug 2024 none Apache-2.0 — Details →
v5.0.0-20240801131707-50d602fb0b55 01 Aug 2024 none Apache-2.0 — Details →
v5.1.1 29 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240729143413-3d2978b93e05 29 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240724101559-f8662ac77cff 24 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240724093443-dbaf0241c733 24 Jul 2024 none Apache-2.0 — Details →
v5.0.1-0.20240722140714-628d402f9385 22 Jul 2024 none Apache-2.0 — Details →
v5.1.0 19 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240719124957-599e3071f61c 19 Jul 2024 none Apache-2.0 — Details →
v5.0.1-0.20240719074859-b73dab82f238 19 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240719072507-9bdc10459925 19 Jul 2024 none Apache-2.0 — Details →
v5.0.1-0.20240718203236-eb852ed63083 18 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240718180806-fde751eb4acd 18 Jul 2024 none Apache-2.0 — Details →
v5.0.1-0.20240718110115-76496d08f129 18 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240718103244-31b5d9977b1c 18 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240703092444-135c4d9fc4f4 03 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240702132056-9ee031266fe5 02 Jul 2024 none Apache-2.0 — Details →
v5.0.1-0.20240702132056-9ee031266fe5 02 Jul 2024 none Apache-2.0 — Details →
v5.0.0-20240625071132-3e63d54cd5a1 25 Jun 2024 none Apache-2.0 — Details →
v5.0.0-20240606064952-245c2e685485 06 Jun 2024 none Apache-2.0 — Details →
v5.0.0 09 May 2024 none Apache-2.0 — Details →
v5.0.0-20240501160458-d313ba5581f9 01 May 2024 none Apache-2.0 — Details →
v5.0.0-provider-rc1 01 May 2024 none Apache-2.0 — Details →
v5.0.0-rc0.0.20240430093053-81c8a9220e04 30 Apr 2024 none Apache-2.0 — Details →
v5.0.0-rc0 25 Apr 2024 none Apache-2.0 — Details →
v5.0.0-alpha1.0.20240425135503-2de60f504c75 25 Apr 2024 none Apache-2.0 — Details →
v5.0.0-alpha1.0.20240424193412-7cd900ad2a74 24 Apr 2024 none Apache-2.0 — Details →
v5.0.0-alpha1.0.20240423100140-781f691e7f89 23 Apr 2024 none Apache-2.0 — Details →
v5.0.0-alpha1 14 Mar 2024 none Apache-2.0 — Details →

All 54 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/cosmos/interchain-security/v5

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Interchain Security: Signer Validation Bypass in github.com/cosmos/interchain-security/v5 N/A high 5.2.0 05 Sep 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/cosmos/interchain-security/v5

Is github.com/cosmos/interchain-security/v5 safe to use?

Vulert records 1 vulnerabilities for github.com/cosmos/interchain-security/v5 in Go: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/cosmos/interchain-security/v5's Vulert package health score?

Vulert scores github.com/cosmos/interchain-security/v5 76/100, which reads as in good shape. 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).

Is the latest version of github.com/cosmos/interchain-security/v5 affected?

No. v5.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of github.com/cosmos/interchain-security/v5 should I use?

v5.2.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/cosmos/interchain-security/v5 have?

1 vulnerability is recorded for github.com/cosmos/interchain-security/v5 in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/cosmos/interchain-security/v5 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cosmos/interchain-security/v5 in the last 12 months, and the oldest entry in this database dates to 05 Sep 2024. 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/cosmos/interchain-security/v5 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/cosmos/interchain-security/v5 for upcoming vulnerabilities?

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