Vulnerability Database · Go · Package report

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

github.com/vmihailenco/msgpack 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 v4.0.4+incompatible i

Updated on 23 Oct 2026

Good news: v4.0.4+incompatible, the version you would install today, has no known vulnerabilities.

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

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

  • Current release v4.0.4+incompatible — 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 90 months ago i
  • Licence BSD-3-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, 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
v0.0.0-20210609114342-5c8f1fd66043 09 Jun 2021 none BSD-3-Clause — Details →
v2.9.2+incompatible 09 Jun 2021 none BSD-3-Clause — Details →
v0.0.0-20190804092921-cd92a145e6d2 04 Aug 2019 none BSD-2-Clause — Details →
v0.0.0-20190804090159-4024476d5c74 04 Aug 2019 none BSD-2-Clause — Details →
v0.0.0-20190804085918-967012b96d3b 04 Aug 2019 none BSD-2-Clause — Details →
v0.0.0-20190804081519-2571bba8efdc 04 Aug 2019 none BSD-2-Clause — Details →
v0.0.0-20190629140232-70e3a1417f36 29 Jun 2019 none BSD-2-Clause — Details →
v0.0.0-20190627120849-8efff0ce4e2a 27 Jun 2019 none BSD-2-Clause — Details →
v0.0.0-20190619163636-6ab7ed835dc3 19 Jun 2019 none BSD-2-Clause — Details →
v0.0.0-20190528140603-28f5bd403628 28 May 2019 none BSD-2-Clause — Details →
v4.0.5-0.20190528140603-28f5bd403628+incompatible 28 May 2019 none BSD-2-Clause — Details →
v0.0.0-20190422135841-5467b4fb032b 22 Apr 2019 none BSD-2-Clause — Details →
v4.0.5-0.20190422135841-5467b4fb032b+incompatible 22 Apr 2019 none BSD-2-Clause — Details →
v0.0.0-20190327140813-c2fc210f30a2 27 Mar 2019 none BSD-2-Clause — Details →
v4.0.4+incompatible 27 Mar 2019 none BSD-2-Clause — Details →
v4.0.3+incompatible 20 Mar 2019 none BSD-2-Clause — Details →
v4.0.3-0.20190319132754-e4394ca80f41+incompatible 19 Mar 2019 none BSD-2-Clause — Details →
v0.0.0-20190212131200-7b65fb0d53fe 12 Feb 2019 none BSD-2-Clause — Details →
v4.0.2+incompatible 23 Jan 2019 none BSD-2-Clause — Details →
v0.0.0-20181023084659-c4fc0fcdd500 23 Oct 2018 none BSD-2-Clause — Details →
v3.3.4-0.20181023084659-c4fc0fcdd500+incompatible 23 Oct 2018 none BSD-2-Clause — Details →
v4.0.1+incompatible 23 Oct 2018 none BSD-2-Clause — Details →
v0.0.0-20181021102514-9f597eca8c34 21 Oct 2018 none BSD-2-Clause — Details →
v4.0.1-0.20181021102514-9f597eca8c34+incompatible 21 Oct 2018 none BSD-2-Clause — Details →
v0.0.0-20180824101621-935c5b540faa 24 Aug 2018 none BSD-2-Clause — Details →
v4.0.0+incompatible 24 Aug 2018 none BSD-2-Clause — Details →
v0.0.0-20180824101311-d79378804108 24 Aug 2018 none BSD-2-Clause — Details →
v3.3.4-0.20180824101311-d79378804108+incompatible 24 Aug 2018 none BSD-2-Clause — Details →
v0.0.0-20180613091515-b5e691b1eb52 13 Jun 2018 none BSD-2-Clause — Details →
v3.3.3+incompatible 13 Jun 2018 none BSD-2-Clause — Details →
v0.0.0-20180517102143-6ab02c0ddf38 17 May 2018 none BSD-2-Clause — Details →
v3.3.2+incompatible 17 May 2018 none BSD-2-Clause — Details →
v0.0.0-20180416070339-a053f3dac71d 16 Apr 2018 none BSD-2-Clause — Details →
v3.3.1+incompatible 16 Apr 2018 none BSD-2-Clause — Details →
v0.0.0-20180319094517-7eb5d7335e1a 19 Mar 2018 none BSD-2-Clause — Details →
v3.3.0+incompatible 19 Mar 2018 none BSD-2-Clause — Details →
v3.2.9+incompatible 15 Mar 2018 none BSD-2-Clause — Details →
v0.0.0-20180206143555-b83fb55e0632 06 Feb 2018 none BSD-2-Clause — Details →
v3.2.8+incompatible 06 Feb 2018 none BSD-2-Clause — Details →
v3.2.7+incompatible 06 Feb 2018 none BSD-2-Clause — Details →
v3.2.7-0.20180131105726-bbe35f532e29+incompatible 31 Jan 2018 none BSD-2-Clause — Details →
v3.2.6+incompatible 31 Jan 2018 none BSD-2-Clause — Details →
v0.0.0-20180130100606-a2885efdac59 30 Jan 2018 none BSD-2-Clause — Details →
v3.2.5+incompatible 30 Jan 2018 none BSD-2-Clause — Details →
v3.2.4+incompatible 17 Jan 2018 none BSD-2-Clause — Details →
v0.0.0-20171215131815-40b1cac89761 15 Dec 2017 none BSD-2-Clause — Details →
v3.2.3+incompatible 15 Dec 2017 none BSD-2-Clause — Details →
v0.0.0-20171130104206-2fd97bb35839 30 Nov 2017 none BSD-2-Clause — Details →
v3.2.2+incompatible 30 Nov 2017 none BSD-2-Clause — Details →
v3.2.1+incompatible 26 Nov 2017 none BSD-2-Clause — Details →
v3.2.1-0.20171125154441-3544e0964893+incompatible 25 Nov 2017 none BSD-2-Clause — Details →
v3.2.1-0.20171120091003-efdbe76f88d1+incompatible 20 Nov 2017 none BSD-2-Clause — Details →
v3.2.1-0.20171120090652-0c39c6e44204+incompatible 20 Nov 2017 none BSD-2-Clause — Details →
v0.0.0-20171029104853-df5e5d20905d 29 Oct 2017 none BSD-2-Clause — Details →
v3.2.0+incompatible 29 Oct 2017 none BSD-2-Clause — Details →
v0.0.0-20171023085424-3cf0238243b4 23 Oct 2017 none BSD-2-Clause — Details →
v3.1.3+incompatible 23 Oct 2017 none BSD-2-Clause — Details →
v3.1.3-0.20170919151936-02a246563e0b+incompatible 19 Sep 2017 none BSD-2-Clause — Details →
v0.0.0-20170812080407-de4b4857c105 12 Aug 2017 none BSD-2-Clause — Details →
v3.1.2+incompatible 12 Aug 2017 none BSD-2-Clause — Details →
v3.1.1+incompatible 30 Jul 2017 none BSD-2-Clause — Details →
v3.1.1-0.20170723113444-23cae422f313+incompatible 23 Jul 2017 none BSD-2-Clause — Details →
v0.0.0-20170622071244-d91c9f43689d 22 Jun 2017 none BSD-2-Clause — Details →
v3.1.0+incompatible 22 Jun 2017 none BSD-2-Clause — Details →
v3.0.1+incompatible 18 Jun 2017 none BSD-2-Clause — Details →
v3.0.1-0.20170618062318-49af4c6054bf+incompatible 18 Jun 2017 none BSD-2-Clause — Details →
v3.0.0+incompatible 17 Jun 2017 none BSD-3-Clause — Details →
v2.0.0-20170502104114-f4f8982de4ef+incompatible 02 May 2017 none BSD-3-Clause — Details →
v2.9.1+incompatible 02 May 2017 none BSD-3-Clause — Details →
v2.9.0+incompatible 01 May 2017 none BSD-3-Clause — Details →
v2.8.5+incompatible 17 Apr 2017 none BSD-3-Clause — Details →
v2.8.5-0.20170415100851-181336d72768+incompatible 15 Apr 2017 none BSD-3-Clause — Details →
v2.8.4+incompatible 14 Mar 2017 none BSD-3-Clause — Details →
v2.8.3+incompatible 03 Jan 2017 none BSD-3-Clause — Details →
v2.8.3-0.20170102153714-8349d80e6e35+incompatible 02 Jan 2017 none BSD-3-Clause — Details →
v2.8.2+incompatible 30 Nov 2016 none BSD-3-Clause — Details →
v2.8.1+incompatible 26 Nov 2016 none BSD-3-Clause — Details →
v2.8.0+incompatible 26 Nov 2016 none BSD-3-Clause — Details →
v2.7.4+incompatible 14 Nov 2016 none BSD-3-Clause — Details →
v2.7.3+incompatible 19 Aug 2016 none BSD-3-Clause — Details →
v2.7.1+incompatible 21 Jul 2016 none BSD-3-Clause — Details →
v2.7.2+incompatible 21 Jul 2016 none BSD-3-Clause — Details →
v2.7.0+incompatible 16 Jul 2016 none BSD-3-Clause — Details →
v2.6.1+incompatible 03 Jul 2016 none BSD-3-Clause — Details →
v2.6.0+incompatible 26 Jun 2016 none BSD-3-Clause — Details →
v2.5.6+incompatible 21 Jun 2016 none BSD-3-Clause — Details →
v2.5.5+incompatible 18 Jun 2016 none BSD-3-Clause — Details →
v2.5.4+incompatible 07 Jun 2016 none BSD-3-Clause — Details →
v2.5.3+incompatible 27 May 2016 none BSD-3-Clause — Details →
v2.5.3-0.20160524063540-f9cca52f7005+incompatible 24 May 2016 none BSD-3-Clause — Details →
v2.5.2+incompatible 23 May 2016 none BSD-3-Clause — Details →
v2.5.2-0.20160517081124-2086c99a6306+incompatible 17 May 2016 none BSD-3-Clause — Details →
v2.5.1+incompatible 13 May 2016 none BSD-3-Clause — Details →
v2.5.0+incompatible 12 May 2016 none BSD-3-Clause — Details →
v2.4.13+incompatible 26 Apr 2016 none BSD-3-Clause — Details →
v2.4.12+incompatible 15 Apr 2016 none BSD-3-Clause — Details →
v2.4.11+incompatible 18 Feb 2016 none BSD-3-Clause — Details →
v2.4.10+incompatible 02 Feb 2016 none BSD-3-Clause — Details →
v2.4.9+incompatible 01 Feb 2016 none BSD-3-Clause — Details →
v2.4.8+incompatible 08 Jan 2016 none BSD-3-Clause — Details →
v2.4.7+incompatible 01 Jan 2016 none — — Details →
v2.4.6+incompatible 30 Dec 2015 none — — Details →
v2.4.5+incompatible 13 Dec 2015 none — — Details →
v2.4.5-0.20151209110228-19f9fa521253+incompatible 09 Dec 2015 none — — Details →
v2.4.4+incompatible 06 Dec 2015 none — — Details →
v2.4.3+incompatible 21 Oct 2015 none — — Details →
v2.4.2+incompatible 30 Aug 2015 none — — Details →
v2.4.1+incompatible 30 Aug 2015 none — — Details →
v2.3.2+incompatible 27 Aug 2015 none — — Details →
v2.3.1+incompatible 22 Aug 2015 none — — Details →
v2.1.5-0.20150417140120-cf7e7d79ee8f+incompatible 17 Apr 2015 none — — Details →
v2.2.1+incompatible 14 Apr 2015 none — — Details →
v2.1.5-0.20150216103509-0aa81421a06c+incompatible 16 Feb 2015 none — — Details →
v2.1.4+incompatible 16 Feb 2015 none — — Details →
v2.1.3+incompatible 19 Jan 2015 none — — Details →
v2.1.2+incompatible 12 Jan 2015 none — — Details →
v2.1.1+incompatible 06 Jan 2015 none — — Details →
v0.0.0-20150102115447-3305938ff32e 02 Jan 2015 none — — Details →
v0.0.0-20141106091106-6004e761984b 06 Nov 2014 none — — Details →
v0.0.0-20140821123208-721f2af77065 21 Aug 2014 none — — Details →

The newest 120 of 128 versions Vulert tracks. 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

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

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

Vulert has no vulnerabilities on record for github.com/vmihailenco/msgpack 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's Vulert package health score?

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

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

No. v4.0.4+incompatible, 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 should I use?

v4.0.4+incompatible 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 have?

0 vulnerabilities are recorded for github.com/vmihailenco/msgpack 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 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/vmihailenco/msgpack 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 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 for upcoming vulnerabilities?

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