Skip to main content
VulnerabilityPublished Updated

CVE-2026-54522: Portable ruby · MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure

Affects portable-rubySource GCVE Database

0
Compare
Authoritative record:CVE-2026-54522· Low 2.1

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

Data as of 19 Nov 2026, 19:37 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.0.6
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 18 Nov 2026.

What to do

Upgrade portable-ruby to 4.0.6.

Affected software

ProductAffectedFixed in
Homebrewportable-rubypkg:brew/portable-rubyOther threatsAffected
  • >=3.4.6 <4.0.6
Fixed in
  • 4.0.6

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

AI-suggested

A patch is available and included in portable-ruby version 4.0.6. Users should upgrade to version 4.0.6 or later to remediate this vulnerability. No additional mitigation steps are required as the fix addresses the root cause by properly resetting internal buffer pointers during the clear operation.

Description

A use-after-free vulnerability exists in portable-ruby's MessagePack::Buffer#clear method, where the buffer returns a memory page to a shared pool but does not reset internal pointers. This leads to a scenario where a second buffer can re-acquire the same memory page, causing cross-buffer information disclosure and potential data corruption within the same process. The flaw requires direct use of the MessagePack::Buffer API with a clear/reuse lifecycle and is not exploitable via plain unpacking of byte streams. The issue is fixed in version 4.0.6.

References

Community reviews

Loading reviews…