Is msgpack 0.6 vulnerable?
RubyGems · 3 releases from 0.6.0 to 0.6.2 · latest msgpack is 1.8.7 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. msgpack 0.6.2, the last 0.6 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.
bundle update --conservative msgpack # Gemfile: '>= 1.8.7'Is your project on an affected msgpack?
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 0.6.2
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
MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure
- Affected
- <1.8.2
- Fixed in
- 1.8.2
Every msgpack 0.6.x release
Affected: 0.6.0 to 0.6.2. Latest msgpack: 1.8.7.
| Version | Known advisories |
|---|---|
| msgpack 0.6.2 | CVE-2026-126366, CVE-2026-54522 |
| msgpack 0.6.1 | CVE-2026-126366, CVE-2026-54522 |
| msgpack 0.6.0 | CVE-2026-126366, CVE-2026-54522 |
Which of your client projects are still on msgpack 0.6?
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.