VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

msgpack5: vulnerability history, versions and safety

msgpack5 is a package in the npm ecosystem. Vulert records 8 vulnerabilities for it across 51 releases, from Mar 2021 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H2 M5 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
7 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all msgpack5 vulnerabilities

Vulert verdict on msgpack5 6.1.0 i

Updated on 22 Oct 2026

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

Package health score 64/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 6.1.0 — unaffected i
  • Vulnerabilities on record 8 over 5 years · 7 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 294 packages i
  • Stars 503 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 msgpack5, 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
6.1.0 26 Sep 2026 none MIT — Details →
6.0.2 15 Jul 2022 H2 M4 L1 MIT Yes Details →
6.0.1 07 Jun 2022 H2 M4 L1 MIT Yes Details →
6.0.0 12 Apr 2022 H2 M4 L1 MIT Yes Details →
5.3.2 25 Mar 2021 H2 M4 L1 MIT Yes Details →
3.6.1 08 Mar 2021 H2 M4 L1 MIT Yes Details →
4.5.1 08 Mar 2021 H2 M4 L1 MIT Yes Details →
5.3.1 05 Mar 2021 H2 M4 L1 MIT Yes Details →
5.3.0 05 Mar 2021 H2 M4 L1 MIT Yes Details →
5.2.1 05 Mar 2021 H2 M4 L1 MIT Yes Details →
5.2.0 02 Mar 2021 H2 M4 L1 MIT Yes Details →
5.1.0 11 Feb 2021 H2 M4 L1 MIT Yes Details →
5.0.0 30 Dec 2020 H2 M4 L1 MIT Yes Details →
4.5.0 30 Dec 2020 H2 M4 L1 MIT Yes Details →
4.4.0 21 Dec 2020 H2 M4 L1 MIT Yes Details →
4.3.0 16 Dec 2020 H2 M4 L1 MIT Yes Details →
4.2.1 17 Sep 2018 H2 M4 L1 MIT Yes Details →
4.2.0 20 May 2018 H2 M4 L1 MIT Yes Details →
4.1.0 17 May 2018 H2 M4 L1 MIT Yes Details →
4.0.2 12 Mar 2018 H2 M4 L1 MIT Yes Details →
4.0.1 13 Jan 2018 H2 M4 L1 MIT Yes Details →
4.0.0 21 Dec 2017 H2 M4 L1 MIT Yes Details →
3.6.0 29 Oct 2017 H2 M5 L1 MIT Yes Details →
3.5.1 29 Aug 2017 H2 M5 L1 MIT Yes Details →
3.5.0 17 Jul 2017 H2 M5 L1 MIT Yes Details →
3.4.1 02 Oct 2016 H2 M5 L1 MIT Yes Details →
3.4.0 22 Jun 2016 H2 M5 L1 MIT Yes Details →
3.3.0 11 Nov 2015 H2 M5 L1 MIT Yes Details →
3.2.0 13 Oct 2015 H2 M5 L1 MIT Yes Details →
3.1.0 28 Jul 2015 H2 M5 L1 MIT Yes Details →
3.0.0 04 Jul 2015 H2 M5 L1 MIT Yes Details →
2.3.1 04 Jul 2015 H2 M5 L1 MIT Yes Details →
2.3.0 22 May 2015 H2 M5 L1 MIT Yes Details →
2.2.0 06 May 2015 H2 M5 L1 MIT Yes Details →
2.1.0 10 Apr 2015 H2 M5 L1 MIT Yes Details →
2.0.0 15 Feb 2015 H2 M5 L1 MIT Yes Details →
1.6.0 13 Feb 2015 H2 M5 L1 MIT Yes Details →
1.5.0 08 Feb 2015 H2 M5 L1 MIT Yes Details →
1.4.0 10 Jan 2015 H2 M5 L1 MIT Yes Details →
1.3.5 27 Nov 2014 H2 M5 L1 MIT Yes Details →
1.3.4 27 Nov 2014 H2 M5 L1 MIT Yes Details →
1.3.3 27 Nov 2014 H2 M5 L1 MIT Yes Details →
1.3.2 18 Nov 2014 H2 M5 L1 MIT Yes Details →
1.3.1 18 Nov 2014 H2 M5 L1 MIT Yes Details →
1.3.0 28 Oct 2014 H2 M5 L1 MIT Yes Details →
1.2.0 07 Oct 2014 H2 M5 L1 MIT Yes Details →
1.1.1 28 Aug 2014 H2 M5 L1 MIT Yes Details →
1.1.0 19 Aug 2014 H2 M5 L1 MIT Yes Details →
1.0.3 29 Jul 2014 H2 M5 L1 MIT Yes Details →
1.0.2 23 Jul 2014 H2 M5 L1 MIT Yes Details →
1.0.1 22 Jul 2014 H2 M5 L1 MIT Yes Details →
1.0.0 21 Jul 2014 H2 M5 L1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for msgpack5

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-107300: msgpack5 Package Stack Exhaustion Vulnerability 7.5 high 6.1.0 08 Oct 2026
CVE-2026-107302: msgpack5 - Out-of-Bounds Read Due to Truncated map32 Header 7.5 high 6.1.0 08 Oct 2026
CVE-2021-21368: Prototype Poisoning in msgpack5 6.7 medium 3.6.1 12 Mar 2021
CVE-2026-107301: msgpack5 Prototype Protection Bypass Vulnerability 6.5 medium 6.1.0 08 Oct 2026
CVE-2026-107299: msgpack5 Unbounded Stream Buffering Due to Reserved Byte Handling 5.9 medium 6.1.0 08 Oct 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 msgpack5

Is msgpack5 safe to use?

Vulert records 8 vulnerabilities for msgpack5 in npm: 0 critical, 2 high, 5 medium and 1 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 msgpack5's Vulert package health score?

Vulert scores msgpack5 64/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 msgpack5 affected?

No. 6.1.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 msgpack5 should I use?

6.1.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 msgpack5 have?

8 vulnerabilities are recorded for msgpack5 in the npm ecosystem: 0 critical, 2 high, 5 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new msgpack5 vulnerabilities disclosed?

7 vulnerabilities were recorded for msgpack5 in the last 12 months, and the oldest entry in this database dates to 12 Mar 2021. 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 msgpack5 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 msgpack5 for upcoming vulnerabilities?

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