Skip to main content
VulnerabilityPublished

CVE-2026-54522: msgpack-ruby · Use After Free

Affects msgpack-rubySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.1 Low : upgrade to 1.8.2 when convenient.

Data as of 29 Oct 2026, 07:15 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.2
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade msgpack-ruby and msgpack to 1.8.2.

Affected software

ProductAffectedFixed in
msgpackmsgpack-rubyAffected
  • <1.8.2
Fixed in
  • 1.8.2
RubyGemsmsgpackpkg:gem/msgpackOther threatsAffected
  • <1.8.2
Fixed in
  • 1.8.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade msgpack-ruby to version 1.8.2 or later, where this use-after-free vulnerability is fixed. No other mitigation or temporary workaround is documented.

Description

MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.2, MessagePack::Buffer#clear in ext/msgpack/buffer.c leaves rmem_last, rmem_end, and rmem_owner stale after _msgpack_buffer_shift_chunk returns an rmem page to the shared pool, allowing a subsequent Buffer#write and a second MessagePack::Buffer to alias the page and disclose or corrupt cross-buffer data. This issue is fixed in version 1.8.2.

References

Community reviews

Loading reviews…