Vulnerability Database · Go · Package report

github.com/vmihailenco/msgpack/v5: vulnerability history, versions and safety

github.com/vmihailenco/msgpack/v5 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

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.

Vulert verdict on github.com/vmihailenco/msgpack/v5 v5.4.1 i

Updated on 23 Oct 2026

Good news: v5.4.1, the version you would install today, has no known vulnerabilities.

Package health score 66/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v5.4.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,675 i
  • OpenSSF scorecard 2/10 i
  • Last release 35 months ago i
  • Licence BSD-2-Clause 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/vmihailenco/msgpack/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-20231026055320-19c91dfdfa06 26 Oct 2023 none BSD-2-Clause — Details →
v5.4.1 26 Oct 2023 none BSD-2-Clause — Details →
v5.4.1-0.20231002121605-3f7bd806fea6 02 Oct 2023 none BSD-2-Clause — Details →
v5.4.0 01 Oct 2023 none BSD-2-Clause — Details →
v5.3.6 01 Oct 2023 none BSD-2-Clause — Details →
v5.0.0-20230726134351-0ac2a568aee9 26 Jul 2023 none BSD-2-Clause — Details →
v5.3.6-0.20230726134351-0ac2a568aee9 26 Jul 2023 none BSD-2-Clause — Details →
v5.3.6-0.20220405065333-233c977ae92b 05 Apr 2022 none BSD-2-Clause — Details →
v5.3.6-0.20220403062837-2a3ff4be63f2 03 Apr 2022 none BSD-2-Clause — Details →
v5.3.6-0.20220126100307-2fc42780a863 26 Jan 2022 none BSD-2-Clause — Details →
v5.3.6-0.20220126090946-52809c6c3cbf 26 Jan 2022 none BSD-2-Clause — Details →
v5.3.6-0.20220123215030-6689e47341ef 23 Jan 2022 none BSD-2-Clause — Details →
v5.3.6-0.20211025061753-6816caa2c2b3 25 Oct 2021 none BSD-2-Clause — Details →
v5.3.5 22 Oct 2021 none BSD-2-Clause — Details →
v5.3.5-0.20211022100923-4a58f167e07a 22 Oct 2021 none BSD-2-Clause — Details →
v5.3.5-0.20210612110230-f09909832580 12 Jun 2021 none BSD-2-Clause — Details →
v5.3.4 28 May 2021 none BSD-2-Clause — Details →
v5.3.3 28 May 2021 none BSD-2-Clause — Details →
v5.3.2 13 May 2021 none BSD-2-Clause — Details →
v5.3.1 24 Mar 2021 none BSD-2-Clause — Details →
v5.3.0 18 Mar 2021 none BSD-2-Clause — Details →
v5.2.2 16 Mar 2021 none BSD-2-Clause — Details →
v5.2.3 16 Mar 2021 none BSD-2-Clause — Details →
v5.2.1 15 Mar 2021 none BSD-2-Clause — Details →
v5.2.1-0.20210225160308-b0653943e7c6 25 Feb 2021 none BSD-2-Clause — Details →
v5.2.0 03 Feb 2021 none BSD-2-Clause — Details →
v5.1.4 03 Jan 2021 none BSD-2-Clause — Details →
v5.1.3 25 Dec 2020 none BSD-2-Clause — Details →
v5.1.2 25 Dec 2020 none BSD-2-Clause — Details →
v5.1.1 23 Dec 2020 none BSD-2-Clause — Details →
v5.1.1-0.20201216144932-f99999d3a42f 16 Dec 2020 none BSD-2-Clause — Details →
v5.1.0 30 Nov 2020 none BSD-2-Clause — Details →
v5.0.0 18 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.3.0.20201117155902-fd4e0e8ce781 17 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.5 17 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.2.0.20201116143425-ee831c71c680 16 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.3 16 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.1.0.20201104082907-3c224f6886a3 04 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.2 04 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-beta.9.0.20201103110302-24ff54846672 03 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-rc.1 03 Nov 2020 none BSD-2-Clause — Details →
v5.0.0-beta.8.0.20201027071323-32d491166197 27 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.9 27 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.8.0.20201026102843-5f912dfde24c 26 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.8.0.20201026102400-ad06fb3d47a5 26 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.7.0.20201025131727-8ee746f1386b 25 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.8 25 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.6.0.20201025090434-abcfc8b5a2b7 25 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.7 25 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.5.0.20201025083714-99f3a9b9907e 25 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.6 25 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.4.0.20201024112442-565e28e4bd7f 24 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.5 24 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.4.0.20201024110116-04ff3c761b70 24 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.3.0.20201023145242-34fa927a3aac 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.4 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.3.0.20201023140726-481cbe1dac1e 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.2.0.20201023075318-16df1ea643e4 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.3 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1.0.20201023064150-eebcf58cbdee 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.2 23 Oct 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1.0.20200831101450-dd83788428a2 31 Aug 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1.0.20200831073451-df6e04850b51 31 Aug 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1.0.20200611075448-9c15726ac118 11 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1.0.20200611074820-26db6ce66ee7 11 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1.0.20200610185811-71144508d2e5 10 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.2.0.20200608105358-e7759683b74a 08 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-beta.1 08 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-rc.4 08 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.2.0.20200605153158-970411c7a84e 05 Jun 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.2.0.20200509080302-e3ede831d771 09 May 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.2.0.20200507103907-026e7aab2268 07 May 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.1.0.20200407075232-9cdaf6a456a7 07 Apr 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.2 07 Apr 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.0.0.20200405091739-629a8092d024 05 Apr 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.1 05 Apr 2020 none BSD-2-Clause — Details →
v5.0.0-20200403123144-656efc8a1c20 03 Apr 2020 none BSD-2-Clause — Details →
v5.0.0-alpha.0 03 Apr 2020 none BSD-2-Clause — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for github.com/vmihailenco/msgpack/v5

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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/vmihailenco/msgpack/v5

Is github.com/vmihailenco/msgpack/v5 safe to use?

Vulert has no vulnerabilities on record for github.com/vmihailenco/msgpack/v5 in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is github.com/vmihailenco/msgpack/v5's Vulert package health score?

Vulert scores github.com/vmihailenco/msgpack/v5 66/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).

Is the latest version of github.com/vmihailenco/msgpack/v5 affected?

No. v5.4.1, 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/vmihailenco/msgpack/v5 should I use?

v5.4.1 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/vmihailenco/msgpack/v5 have?

0 vulnerabilities are recorded for github.com/vmihailenco/msgpack/v5 in the Go ecosystem: 0 critical, 0 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/vmihailenco/msgpack/v5 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/vmihailenco/msgpack/v5 in the last 12 months. 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/vmihailenco/msgpack/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/vmihailenco/msgpack/v5 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/vmihailenco/msgpack/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.