VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

msgpack: vulnerability history, versions and safety

msgpack is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 88 releases, first recorded in Jul 2026. 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 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 30 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all msgpack vulnerabilities

Vulert verdict on msgpack 1.8.5 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.8.5 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 30 Jul 2026 i
  • Highest CVSS 2.1 i
  • With no published fix 0 i
  • Stars 789 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by RubyGems, 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 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
1.8.5 11 Sep 2026 none Apache-2.0 — Details →
1.8.4 28 Jul 2026 none Apache-2.0 — Details →
1.8.3 10 Jun 2026 none Apache-2.0 — Details →
1.8.2 09 Jun 2026 none Apache-2.0 — Details →
1.8.1 28 May 2026 L1 Apache-2.0 Yes Details →
1.8.0 06 Feb 2025 L1 Apache-2.0 Yes Details →
1.7.5 11 Nov 2024 L1 Apache-2.0 Yes Details →
1.7.4 11 Nov 2024 L1 Apache-2.0 Yes Details →
1.7.3 04 Oct 2024 L1 Apache-2.0 Yes Details →
1.7.2 18 Jul 2023 L1 Apache-2.0 Yes Details →
1.7.1 19 May 2023 L1 Apache-2.0 Yes Details →
1.7.0 29 Mar 2023 L1 Apache-2.0 Yes Details →
1.6.1 03 Mar 2023 L1 Apache-2.0 Yes Details →
1.6.0 30 Sep 2022 L1 Apache-2.0 Yes Details →
1.5.6 23 Aug 2022 L1 Apache-2.0 Yes Details →
1.5.5 22 Aug 2022 L1 Apache-2.0 Yes Details →
1.5.4 25 Jul 2022 L1 Apache-2.0 Yes Details →
1.5.3 01 Jul 2022 L1 Apache-2.0 Yes Details →
1.5.2 27 May 2022 L1 Apache-2.0 Yes Details →
1.5.1 07 Apr 2022 L1 Apache-2.0 Yes Details →
1.5.0 06 Apr 2022 L1 Apache-2.0 Yes Details →
1.4.5 15 Feb 2022 L1 Apache-2.0 Yes Details →
1.4.4 22 Jan 2022 L1 Apache-2.0 Yes Details →
1.4.3 20 Jan 2022 L1 Apache-2.0 Yes Details →
1.4.2 01 Feb 2021 L1 Apache-2.0 Yes Details →
1.4.0.pre1 08 Sep 2020 L1 Apache-2.0 Yes Details →
1.3.3 05 Feb 2020 L1 Apache-2.0 Yes Details →
1.3.2 04 Feb 2020 L1 Apache-2.0 Yes Details →
1.3.1 05 Aug 2019 L1 Apache-2.0 Yes Details →
1.3.0 20 Jun 2019 L1 Apache-2.0 Yes Details →
1.2.10 19 Apr 2019 L1 Apache-2.0 Yes Details →
1.2.9 13 Mar 2019 L1 Apache-2.0 Yes Details →
1.2.8 11 Mar 2019 L1 Apache-2.0 Yes Details →
1.2.7 01 Mar 2019 L1 Apache-2.0 Yes Details →
1.2.6 08 Jan 2019 L1 Apache-2.0 Yes Details →
1.2.5 08 Jan 2019 L1 Apache-2.0 Yes Details →
1.2.4 02 Mar 2018 L1 Apache-2.0 Yes Details →
1.2.3 02 Mar 2018 L1 Apache-2.0 Yes Details →
1.2.2 11 Jan 2018 L1 Apache-2.0 Yes Details →
1.2.0 07 Dec 2017 L1 Apache-2.0 Yes Details →
1.1.0 28 Feb 2017 L1 Apache-2.0 Yes Details →
1.0.3 25 Jan 2017 L1 Apache-2.0 Yes Details →
1.0.2 17 Oct 2016 L1 Apache-2.0 Yes Details →
1.0.1 17 Oct 2016 L1 Apache-2.0 Yes Details →
1.0.0 08 Jul 2016 L1 Apache-2.0 Yes Details →
0.7.6 10 May 2016 L1 Apache-2.0 Yes Details →
0.7.5 06 Apr 2016 L1 Apache-2.0 Yes Details →
0.7.4 08 Jan 2016 L1 Apache-2.0 Yes Details →
0.7.3 07 Jan 2016 L1 Apache-2.0 Yes Details →
0.7.2 06 Jan 2016 L1 Apache-2.0 Yes Details →
0.7.1 20 Nov 2015 L1 Apache-2.0 Yes Details →
0.7.0 24 Oct 2015 L1 Apache-2.0 Yes Details →
0.7.0dev1 05 Sep 2015 L1 Apache-2.0 Yes Details →
0.6.2 22 Jul 2015 L1 Apache-2.0 Yes Details →
0.6.1 01 Jul 2015 L1 Apache-2.0 Yes Details →
0.6.0 26 May 2015 L1 Apache-2.0 Yes Details →
0.5.12 21 May 2015 L1 Apache-2.0 Yes Details →
0.6.0pre1 18 May 2015 L1 Apache-2.0 Yes Details →
0.5.11 04 Feb 2015 L1 Apache-2.0 Yes Details →
0.5.10 09 Jan 2015 L1 Apache-2.0 Yes Details →
0.5.9 06 Oct 2014 L1 Apache-2.0 Yes Details →
0.5.8 14 Dec 2013 L1 Apache-2.0 Yes Details →
0.5.7 13 Nov 2013 L1 Apache-2.0 Yes Details →
0.5.6 24 Sep 2013 L1 Apache-2.0 Yes Details →
0.5.5 13 May 2013 L1 — Yes Details →
0.5.4 15 Mar 2013 L1 — Yes Details →
0.5.3 14 Feb 2013 L1 — Yes Details →
0.5.2 07 Feb 2013 L1 — Yes Details →
0.5.1 24 Dec 2012 L1 — Yes Details →
0.5.0 20 Dec 2012 L1 — Yes Details →
0.4.7 06 May 2012 L1 — Yes Details →
0.4.6 08 Aug 2011 L1 — Yes Details →
0.4.5 09 May 2011 L1 — Yes Details →
0.4.4 28 Nov 2010 L1 — Yes Details →
0.4.3 29 Jun 2010 L1 — Yes Details →
0.4.2 03 Jun 2010 L1 — Yes Details →
0.4.1 26 May 2010 L1 — Yes Details →
0.4.0 25 May 2010 L1 — Yes Details →
0.3.9 23 Apr 2010 L1 — Yes Details →
0.3.8 22 Apr 2010 L1 — Yes Details →
0.3.7 06 Apr 2010 L1 — Yes Details →
0.3.6 01 Apr 2010 L1 — Yes Details →
0.3.5 01 Apr 2010 L1 — Yes Details →
0.3.4 31 Mar 2010 L1 — Yes Details →
0.3.3 02 Mar 2010 L1 — Yes Details →
0.3.2 10 Dec 2009 L1 — Yes Details →
0.2.2 05 Aug 2009 L1 — Yes Details →
0.0.1 25 Jul 2009 L1 — Yes Details →
0.2.0 25 Jul 2009 L1 — Yes Details →
0.2.1 25 Jul 2009 L1 — Yes Details →
0.3.0 25 Jul 2009 L1 — Yes Details →
0.3.1 25 Jul 2009 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for msgpack

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54522: MessagePack Buffer Use-After-Free Vulnerability Leading to Cross-Buffer Disclosure 2.1 low 1.8.2 30 Jul 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: 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 msgpack

Is msgpack safe to use?

Vulert records 1 vulnerabilities for msgpack in RubyGems: 0 critical, 0 high, 0 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 msgpack's Vulert package health score?

Vulert scores msgpack 78/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 msgpack affected?

No. 1.8.5, 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 msgpack should I use?

1.8.5 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 msgpack have?

1 vulnerability is recorded for msgpack in the RubyGems ecosystem: 0 critical, 0 high, 0 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 msgpack vulnerabilities disclosed?

1 vulnerability was recorded for msgpack in the last 12 months, and the oldest entry in this database dates to 30 Jul 2026. 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 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 msgpack for upcoming vulnerabilities?

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