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.
CVE-2026-32829
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EPSS
- 44.8%
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 30, 2026
Advisory Details (10)
Auto-updated Jul 3, 2026Affected: Red Hat Enterprise Linux 10",
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32829.json2448271 – (CVE-2026-32829, GHSA-vvp9-7p8x-rfvv) CVE-2026-32829 lz4_flex: lz4_flex's decompression can leak information from uninitialized memory or reused output buffer
https://bugzilla.redhat.com/show_bug.cgi?id=2448271RUSTSEC-2026-0041: lz4_flex: Decompressing invalid data can leak information from uninitialized memory or reused output buffer › RustSec Advisory Database
https://rustsec.org/advisories/RUSTSEC-2026-0041.htmlDecompressing invalid data can leak information from uninitialized memory or reused output buffer · Advisory · PSeitz/lz4_flex · GitHub
https://github.com/PSeitz/lz4_flex/security/advisories/GHSA-vvp9-7p8x-rfvvcommit 055502ee5d29 (PSeitz/lz4_flex)
Patch available: PSeitz/lz4_flex 0.13.0 (contains commit 055502ee5d29)
https://github.com/PSeitz/lz4_flex/commit/055502ee5d297ecd6bf448ac91c055c7f6df9b6dVendor Advisories for CVE-2026-32829(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:22862Red Hat Product SecurityHigh
Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.4.5
- RHSA-2026:19712Red Hat Product SecurityCritical
Red Hat Security Advisory: RHOAI 3.3.3 - Red Hat OpenShift AI
- RHSA-2026:16354Red Hat Product SecurityHigh
Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.5.1
- RHSA-2026:11800Red Hat Product SecurityHigh
Red Hat Security Advisory: Logging for Red Hat OpenShift - 6.2.10
Patch Availability(4)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | openshift-logging/vector-rhel9:1780052069 | 2026-06-03 | redhat |
| redhat | rhoai/odh-llm-d-inference-scheduler-rhel9:1778263962 | 2026-05-20 | redhat |
| redhat | openshift-logging/vector-rhel9:1777574710 | 2026-05-12 | redhat |
| redhat | openshift-logging/vector-rhel9:1776894389 | 2026-04-29 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| lz4_flex | — | 0.11.6 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 04:33 UTCEG score recompute
- 2026-06-30 04:33 UTCVendor advisory
- 2026-06-30 04:32 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-201 · CWE-823
Frequently asked(5)
What is CVE-2026-32829?
When was CVE-2026-32829 disclosed?
Is CVE-2026-32829 actively exploited?
What is the CVSS score of CVE-2026-32829?
How do I remediate CVE-2026-32829?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32829
Is Your Infrastructure Affected by CVE-2026-32829?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.