What is CVE-2025-31115?
XZ Utils provide a general-purpose data-compression library plus command-line tools. In XZ Utils 5.3.3alpha to 5.8.0, the multithreaded .xz decoder in liblzma has a bug where invalid input can at least result in a crash. The effects include heap use after free and writing to an address based on the null pointer plus an offset. Applications and libraries that use the lzma_stream_decoder_mt function are affected. The bug has been fixed in XZ Utils 5.8.1, and the fix has been committed to the v5.4, v5.6, v5.8, and master branches in the xz Git repository. No new release packages will be made from the old stable branches, but a standalone patch is available that applies to all affected releases.
The record classifies CVE-2025-31115 under weakness classes CWE-366, CWE-416, CWE-476, CWE-826. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 595 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 8.7 — High (derived from score)
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 - EPSS (FIRST)
- 0.6% probability of exploitation in the next 30 days, higher than 50.1% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 8.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2025-04-03
Is CVE-2025-31115 being exploited?
Weaponised exploit code for CVE-2025-31115 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 26 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
- tukaani-project: xz
How to fix CVE-2025-31115
No vendor patch reference has been recorded for CVE-2025-31115 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2025-31115
1 tracked threat in the Threadlinqs corpus references CVE-2025-31115, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories.