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 duplicitySource GCVE Database

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

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

Data as of 1 Nov 2026, 02:07 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.1.0_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 31 Oct 2026.

What to do

Upgrade duplicity to 3.1.0_1.

Affected software

ProductAffectedFixed in
Homebrewduplicitypkg:brew/duplicityOther threatsAffected
  • >=1.0.1 <3.1.0_1
Fixed in
  • 3.1.0_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 3.1.0_1 to prevent crashes from Unpacker reuse after errors. Additionally, do not reuse the Streaming Unpacker or stream after an error occurs; instead, discard them and create new instances. This approach is the correct solution to avoid both crashes and incorrect data processing.

Description

MessagePack for Python's Unpacker component has a vulnerability where reusing the same Unpacker instance after an error can cause a process crash (segmentation fault). This can lead to denial-of-service (DoS) conditions if untrusted input triggers repeated errors. The issue is fixed in version 3.1.0_1. Users are advised to create a new Unpacker after an error instead of reusing the existing one. The patch prevents crashes but does not change the need to discard the Unpacker after errors to avoid incorrect data processing.

References

Community reviews

Loading reviews…