XZ Utils: the version number was not the whole story
PERIOD
Public disclosure March 29, 2024
EDITION
Short field file
REVIEWED
2026-11-19
The short version
On March 29, 2024, Andres Freund disclosed a backdoor in upstream XZ/liblzma. His investigation began with unusual SSH CPU use and diagnostic errors. The affected release tarballs were XZ Utils 5.6.0 and 5.6.1.
Same label, different contents
Freund’s report distinguished material in the source repository from an activating component present in the distributed release tarballs. It also described build prerequisites. Seeing an affected version label was not enough to establish that every installation contained an active backdoor.
What the project confirmed
Maintainer Lasse Collin states that the compromised tarballs were created and signed by Jia Tan. He distinguishes that account’s GitHub access from his own control of the main project website and other infrastructure. A valid signature identifies a signing key; it is not a guarantee that the signed content is safe.
What we should not pretend to know
An account name is not a verified real-world identity. These sources do not justify assigning a nationality or state sponsor. This short account also makes no claim about a confirmed population of exploited victims.
From the workbench
“Which version?” is a starting question. “Which artifact, built how, and supplied by whom?” can be the more useful follow-up. That is the lesson here: check the thing you actually installed, not just its label.
Historical file, not a live advisory
This describes the 2024 disclosure. For current software decisions, use maintained distribution and vendor guidance. It does not treat the conditions in the initial report as a complete modern exposure checklist.
