CVE-2026-32829

HIGHNVD 7.57.5
EchelonGraph scoreLOW confidence

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).

Triggered by: NVD CVSS baseline
Sources: nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

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, 2026
Patch available. Sources: github_commit, github, redhat.
redhat

2448271 – (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=2448271
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-32829
generic

RUSTSEC-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.html
github Patch Available

Decompressing 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-rfvv
github_commit Patch Available

commit 055502ee5d29 (PSeitz/lz4_flex)

Patch available: PSeitz/lz4_flex 0.13.0 (contains commit 055502ee5d29)

https://github.com/PSeitz/lz4_flex/commit/055502ee5d297ecd6bf448ac91c055c7f6df9b6d

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-logging/vector-rhel9:17800520692026-06-03redhat
redhatrhoai/odh-llm-d-inference-scheduler-rhel9:17782639622026-05-20redhat
redhatopenshift-logging/vector-rhel9:17775747102026-05-12redhat
redhatopenshift-logging/vector-rhel9:17768943892026-04-29redhat

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)
PackageVulnerable rangeFixed inDependents
lz4_flex0.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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 04:33 UTCEG score recompute
  10. 2026-06-30 04:33 UTCVendor advisory
  11. 2026-06-30 04:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-32829?
CVE-2026-32829 is a high vulnerability published on March 20, 2026. lz4flex 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…
When was CVE-2026-32829 disclosed?
CVE-2026-32829 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32829 actively exploited?
CVE-2026-32829 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32829?
CVE-2026-32829 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-32829?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32829, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32829

Explore →

Is Your Infrastructure Affected by CVE-2026-32829?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.