Skip to main content
VulnerabilityPublished

CVE-2025-31115: Xz clib · Use after free in multithreaded lzma (.xz) decoder

Affects xz-clibSource GCVE Database

0
Compare
Authoritative record:CVE-2025-31115· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 5.8.1 soon.

Data as of 13 Nov 2026, 18:41 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.8.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2025

  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 13 Nov 2026.

What to do

Upgrade xz-clib to 5.8.1.

Affected software

ProductAffectedFixed in
Hackagexz-clibAffected
  • >=5.6.3 <5.8.1
Fixed in
  • 5.8.1

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

AI-suggested

Upgrade affected software to version 5.8.1 or later, where the vulnerability is fixed. The vendor has provided patches and official fixes. No other mitigation is indicated or required.

Description

A use-after-free vulnerability exists in the multithreaded LZMA (.xz) decoder of XZ Utils versions 5.6.3 through 5.8.0. This flaw can cause heap corruption and invalid memory writes when processing specially crafted input. Applications using the lzma_stream_decoder_mt function are affected. The issue is fixed in version 5.8.1. The Haskell xz-clib library, which vendors the C implementation, is affected, but the xz package itself is not because it does not use the multithreaded decoder.

References

Community reviews

Loading reviews…