Skip to main content
VulnerabilityPublished Updated

CVE-2026-57585: MessagePack for Python · Out-of-bounds read / crash on Unpacker reuse after a caught error

Affects bztSource GCVE Database

0
Compare
Authoritative record:CVE-2026-57585· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.16.51_1 soon.

Data as of 19 Nov 2026, 19:37 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.16.51_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 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 bzt to 1.16.51_1.

Affected software

ProductAffectedFixed in
Homebrewbztpkg:brew/bztOther threatsAffected
  • >=1.16.21 <1.16.51_1
Fixed in
  • 1.16.51_1

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

AI-suggested

Apply the official patch available in version 1.16.51_1 to prevent segmentation faults caused by incorrect Unpacker reuse. Additionally, do not reuse the same Unpacker instance after an error occurs; instead, discard the Stream and Streaming Unpacker and create new instances. This approach is the correct solution to ensure data integrity and prevent crashes.

Description

A vulnerability in MessagePack for Python's Unpacker allows a process crash (SEGV) when the Unpacker is reused after an error occurs. This can lead to denial-of-service (DoS) conditions if untrusted input triggers repeated errors. The issue is fixed in version 1.16.51_1. Users should avoid reusing the same Unpacker after errors and instead create a new instance to ensure correct operation and prevent crashes.

References

Community reviews

Loading reviews…