{"id":"GHSA-vvp9-7p8x-rfvv","revision":"c2123912f41d4e44afa22d4178e0c0c5","records":[{"revision":"c2123912f41d4e44afa22d4178e0c0c5","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-vvp9-7p8x-rfvv","aliases":["CVE-2026-32829","RUSTSEC-2026-0041"],"title":"lz4_flex's decompression can leak information from uninitialized memory or reused output buffer","description":"### Summary\nDecompressing invalid LZ4 data can leak data from uninitialized memory, or can leak content from previous decompression operations when reusing an output buffer.\n\n### Details\nThe LZ4 block format defines a \"match copy operation\" which duplicates previously written data or data from the user-supplied dict. The position of that data is defined by an _offset_. The data is copied within the output buffer from the _offset_ to the current output position.\nHowever, lz4_flex did not properly detect invalid and out-of-bounds _offset_ values properly, causing it to copy uninitialized data from the output buffer.\n\nOnly the block based API functions are affected: \n`lz4_flex::block::{decompress_into, decompress_into_with_dict}`\n\nWhen safe-decode is disabled _additionally_ these functions are affected\n`lz4_flex::block::{decompress, decompress_with_dict, decompress_size_prepended, decompress_size_prepended_with_dict}`\n\nAll `frame` APIs are _not_ affected.\n\nThere are two affected use cases:\n- decompressing LZ4 data with the `unsafe` implementation (`safe-decode` feature flag disabled, which is enabled by default):\ncan leak content of uninitialized memory as decompressed result\n- decompressing LZ4 data into a reused, user-supplied `output` buffer (affects the `safe-decode` feature as well):\ncan leak the previous contents of the output buffer as decompressed result\n\n### Impact\nLeakage of data from uninitialized memory or content from previous decompression operations, possibly revealing sensitive information and secrets.\n\n### Mitigation\nlz4_flex 0.12.1 and 0.11.6 fixes this issue without requiring changes in user code.\n\nIf you cannot upgrade, you can mitigate this vulnerability by zeroing the output buffer before calling `block::decompress_into` or  `block::decompress_into_with_dict` (only block based API is affected, frame API is not affected). Additionally the the `safe-decode` feature flag should be enabled.","state":0,"publishedAt":"2026-03-16T20:48:08+00:00","modifiedAt":"2026-09-10T03:50:41.3147108+00:00","affected":[{"ecosystem":"crates.io","name":"lz4_flex","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"0.11.6"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"crates.io","name":"lz4_flex","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.12.0"},{"kind":"fixed","version":"0.12.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"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","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/PSeitz/lz4_flex/security/advisories/GHSA-vvp9-7p8x-rfvv","https://nvd.nist.gov/vuln/detail/CVE-2026-32829","https://github.com/PSeitz/lz4_flex/commit/055502ee5d297ecd6bf448ac91c055c7f6df9b6d","https://github.com/PSeitz/lz4_flex","https://rustsec.org/advisories/RUSTSEC-2026-0041.html"],"sourceUrl":"https://github.com/advisories/GHSA-vvp9-7p8x-rfvv","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-vvp9-7p8x-rfvv","identifiers":["GHSA-vvp9-7p8x-rfvv","CVE-2026-32829","RUSTSEC-2026-0041"]},"retained":false,"historicalAffected":[]}],"coverage":[]}