Decompressing invalid data can leak information from uninitialized memory or reused output buffer
Historical advisory saved 24 Oct 2026 13:19:54 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0041
PublishedDecompressing invalid LZ4 data with the block API can leak data from uninitialized memory, or leak content from previous decompression operations when reusing an output buffer. The LZ4 block format defines a "match copy operation" which duplicates previously written data or data from a user-supplied dict. The position of that data is defined by an _offset_. `lz4_flex` did not properly validate _offset_ values, causing it to copy data from outside the initialized portion of the output buffer. Two scenarios are affected: - Decompressing with the `unsafe` implementation (`safe-decode` feature flag disabled, which is the default): can leak content of uninitialized memory as part of the decompressed result. - Decompressing into a reused, user-supplied output buffer (also affects `safe-decode`): can leak the previous contents of the output buffer as part of the decompressed result. Only the block-based APIs are affected. All frame APIs are unaffected. The flaw was corrected in versions 0.11.6 and 0.12.1 by properly validating offset values during decompression. If upgrading is not possible, the issue can be mitigated by zeroing the output buffer before each call to the affected functions and enabling the `safe-decode` feature flag.
- Source published
- 17 Mar 2026 12:00:00 UTC
- Source modified
- 17 Mar 2026 16:15:16 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N