CVE-2026-32829

lz4_flex: Decompression can leak information from uninitialized memory or reused output buffer

Published Mar 20, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
lz4_flex is a pure Rust implementation of LZ4 compression/decompression. In versions 0.11.5 and below, and 0.12.0, decompressing invalid LZ4 data can leak sensitive information from uninitialized memory or from previous decompression operations. The library fails to properly validate offset values during LZ4 "match copy operations," allowing out-of-bounds reads from the output buffer. The block-based API functions (`decompress_into`, `decompress_into_with_dict`, and others when `safe-decode` is disabled) are affected, while all frame APIs are unaffected. The impact is potential exposure of sensitive data and secrets through crafted or malformed LZ4 input. This issue has been fixed in versions 0.11.6 and 0.12.1.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-vvp9-7p8x-rfvv lz4_flex's decompression can leak information from uninitialized memory or reused output buffer
History
Type Values Removed Values Added
CPEs cpe:2.3:a:pseitz:lz4_flex:*:*:*:*:*:rust:*:*
cpe:2.3:a:pseitz:lz4_flex:0.12.0:*:*:*:*:rust:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description No description is available for this CVE. lz4_flex is a pure Rust implementation of LZ4 compression/decompression. In versions 0.11.5 and below, and 0.12.0, decompressing invalid LZ4 data can leak sensitive information from uninitialized memory or from previous decompression operations. The library fails to properly validate offset values during LZ4 "match copy operations," allowing out-of-bounds reads from the output buffer. The block-based API functions (`decompress_into`, `decompress_into_with_dict`, and others when `safe-decode` is disabled) are affected, while all frame APIs are unaffected. The impact is potential exposure of sensitive data and secrets through crafted or malformed LZ4 input. This issue has been fixed in versions 0.11.6 and 0.12.1.
Title lz4_flex: lz4_flex's decompression can leak information from uninitialized memory or reused output buffer lz4_flex: Decompression can leak information from uninitialized memory or reused output buffer
Weaknesses CWE-201
References
Metrics cvssV4_0

{'score': 8.2, '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'}

Type Values Removed Values Added
First Time appeared Pseitz
Pseitz lz4 Flex
Vendors & Products Pseitz
Pseitz lz4 Flex
Type Values Removed Values Added
Description No description is available for this CVE.
Title lz4_flex: lz4_flex's decompression can leak information from uninitialized memory or reused output buffer
Weaknesses CWE-823
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

threat_severity

Important

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 17, 2026, 12:04 PM
Reserved
Mar 16, 2026, 5:35 PM
Status
Modified
Published
Mar 20, 2026, 1:15 AM
Modified
Sep 17, 2026, 12:17 PM
Severity
Important
Public date
Mar 16, 2026, 8:48 PM