Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-34743: CWE-122: Heap-based Buffer Overflow in tukaani-project xz

0
Low
VulnerabilityCVE-2026-34743cvecve-2026-34743cwe-122
Published: Thu Apr 02 2026 (04/02/2026, 18:36:37 UTC)
Source: CVE Database V5
Vendor/Project: tukaani-project
Product: xz

Description

XZ Utils provide a general-purpose data-compression library plus command-line tools. Prior to version 5.8.3, if lzma_index_decoder() was used to decode an Index that contained no Records, the resulting lzma_index was left in a state where where a subsequent lzma_index_append() would allocate too little memory, and a buffer overflow would occur. This issue has been patched in version 5.8.3.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 19:28:57 UTC

Technical Analysis

CVE-2026-34743 is a heap-based buffer overflow vulnerability identified in the xz compression library maintained by the tukaani-project. The issue arises specifically when the function lzma_index_decoder() decodes an Index structure containing zero Records. In this scenario, the resulting lzma_index object remains improperly initialized, causing the subsequent call to lzma_index_append() to allocate less memory than required. This insufficient allocation leads to a heap buffer overflow when appending data. The vulnerability is classified under CWE-122 (Heap-based Buffer Overflow). Exploiting this flaw could result in memory corruption, potentially causing application crashes or undefined behavior. However, the CVSS 4.0 base score is low (1.7), reflecting limited impact and exploitation complexity. The vulnerability does not require privileges, authentication, or user interaction, and no known exploits have been reported in the wild. The issue was addressed and patched in xz version 5.8.3, which corrects the memory allocation logic to prevent buffer overflow conditions. The xz utility and library are commonly used in Unix-like operating systems for data compression and decompression, making this vulnerability relevant to a broad range of software environments that rely on xz for handling compressed data streams.

Potential Impact

The potential impact of CVE-2026-34743 is relatively low due to its low CVSS score and the absence of known exploits. Successful exploitation could lead to heap memory corruption, which might cause application crashes or denial of service in processes using vulnerable xz versions. While the vulnerability does not directly enable privilege escalation or remote code execution, memory corruption issues can sometimes be leveraged in complex attack chains. Organizations that use xz compression in automated workflows, software packaging, or data processing pipelines could experience stability issues if the vulnerability is triggered. However, the requirement to process a specific malformed Index with no Records limits the likelihood of accidental exploitation. Since no user interaction or authentication is required, remote attackers could potentially trigger the flaw by supplying crafted compressed data to vulnerable systems. Overall, the impact is mostly confined to availability and integrity of affected applications rather than confidentiality or system-wide compromise.

Mitigation Recommendations

To mitigate CVE-2026-34743, organizations should upgrade all instances of the xz utility and library to version 5.8.3 or later, where the vulnerability is patched. For environments where immediate upgrade is not feasible, consider implementing input validation or filtering to detect and block compressed data containing empty Index structures before processing. Monitoring logs and application behavior for crashes or anomalies related to xz usage can help identify exploitation attempts. Security teams should also review software supply chains and automated build systems that utilize xz to ensure they are not processing untrusted or malformed compressed files. Employing runtime protections such as heap memory corruption mitigations (e.g., ASLR, heap canaries) can reduce the risk of exploitation impact. Finally, maintain awareness of updates from the tukaani-project and related Linux distributions to promptly apply security patches.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-30T19:17:10.224Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69cec35ae6bfc5ba1dfb4cd9

Added to database: 4/2/2026, 7:28:26 PM

Last enriched: 4/2/2026, 7:28:57 PM

Last updated: 4/3/2026, 5:52:44 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses