Is msgpack 1.7 vulnerable?

RubyGems · 6 releases from 1.7.0 to 1.7.5 · latest msgpack is 1.8.7 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. msgpack 1.7.5, the last 1.7 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2026-126366, CVE-2026-54522. Upgrade to 1.8.7 or later to fix all of them.

Upgrade with:bundle update --conservative msgpack # Gemfile: '>= 1.8.7'

Is your project on an affected msgpack?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting msgpack 1.7.5

  • HighCVE-2026-126366GHSA-73v3-wf97-vpgj12 Nov 2026

    msgpack-ruby JRuby decoder makes uncapped header-count allocations; a 5-byte message forces multi-GiB OOM

    Affected
    <1.8.7
    Fixed in
    1.8.7
  • LowCVE-2026-54522GHSA-4mrv-5p47-p93830 Jul 2026

    MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure

    Affected
    <1.8.2
    Fixed in
    1.8.2

Every msgpack 1.7.x release

Affected: 1.7.0 to 1.7.5. Latest msgpack: 1.8.7.

VersionKnown advisories
msgpack 1.7.5CVE-2026-126366, CVE-2026-54522
msgpack 1.7.4CVE-2026-126366, CVE-2026-54522
msgpack 1.7.3CVE-2026-126366, CVE-2026-54522
msgpack 1.7.2CVE-2026-126366, CVE-2026-54522
msgpack 1.7.1CVE-2026-126366, CVE-2026-54522
msgpack 1.7.0CVE-2026-126366, CVE-2026-54522

Which of your client projects are still on msgpack 1.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact msgpack version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other msgpack versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.