CVE-2026-32829

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. 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: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

Published

March 20, 2026

Last Modified

September 17, 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 / EcosystemFix (by version range) / 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

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
lz4_flex—
  • every version up to 0.11.6: fixed in 0.11.6
  • 0.12.0 up to 0.12.1: fixed in 0.12.1
  • 0.0.0-0 up to 0.11.6: fixed in 0.11.6
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-lz4-flex0.11.3-1, 0.11.3-2, 0.13.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-lz4-flex0.11.3-1, 0.11.3-2
  • every version up to 0.13.0-1: fixed in 0.13.0-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 25× 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.

Showing the most recent 100 of 154 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-01 19:49 UTCEPSS rescore
  4. 2026-09-30 15:03 UTCEPSS rescore
  5. 2026-09-28 13:51 UTCEPSS rescore
  6. 2026-09-27 13:48 UTCEPSS rescore
  7. 2026-09-26 15:58 UTCEPSS rescore
  8. 2026-09-26 00:26 UTCEPSS rescore
  9. 2026-09-20 20:15 UTCEPSS rescore
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 19:30 UTCEPSS rescore
  13. 2026-09-17 12:19 UTCVendor advisory
  14. 2026-09-17 12:11 UTCEG score recompute
  15. 2026-09-17 12:11 UTCVendor advisory
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-12 15:01 UTCEPSS rescore
  20. 2026-09-11 14:52 UTCEPSS rescore
  21. 2026-09-10 09:34 UTCEPSS rescore
  22. 2026-09-08 22:00 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 13:30 UTCVendor advisory
  2. 2026-09-04 12:25 UTCEG score recompute
  3. 2026-09-04 12:25 UTCVendor advisory
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:11 UTCEPSS rescore
  6. 2026-09-01 13:53 UTCEPSS rescore
  7. 2026-09-01 04:39 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-25 13:26 UTCVendor advisory
  16. 2026-08-25 12:22 UTCEG score recompute
  17. 2026-08-25 12:22 UTCVendor advisory
  18. 2026-08-24 14:17 UTCEPSS rescore
  19. 2026-08-24 13:31 UTCVendor advisory
  20. 2026-08-24 12:27 UTCEG score recompute
  21. 2026-08-24 12:27 UTCVendor advisory
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-19 17:03 UTCEPSS rescore
  27. 2026-08-19 12:28 UTCVendor advisory
  28. 2026-08-19 12:12 UTCEG score recompute
  29. 2026-08-19 12:12 UTCVendor advisory
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-17 12:13 UTCEG score recompute
  33. 2026-08-17 12:13 UTCVendor advisory
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 11:06 UTCEG score recompute
  36. 2026-08-16 11:06 UTCVendor advisory
  37. 2026-08-16 02:14 UTCEPSS rescore
  38. 2026-08-15 01:30 UTCEPSS rescore
  39. 2026-08-14 20:04 UTCVendor advisory
  40. 2026-08-14 07:17 UTCEG score recompute
  41. 2026-08-14 07:17 UTCVendor advisory
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-12 21:58 UTCEG score recompute
  44. 2026-08-12 21:58 UTCVendor advisory
  45. 2026-08-12 13:50 UTCEPSS rescore
  46. 2026-08-12 02:17 UTCEG score recompute
  47. 2026-08-12 02:17 UTCVendor advisory
  48. 2026-08-11 13:24 UTCVendor advisory
  49. 2026-08-11 12:24 UTCVendor advisory
  50. 2026-08-11 04:28 UTCEG score recompute
  51. 2026-08-11 04:28 UTCVendor advisory
  52. 2026-08-11 00:00 UTCEPSS rescore
  53. 2026-08-10 13:22 UTCVendor advisory
  54. 2026-08-10 12:27 UTCVendor advisory
  55. 2026-08-10 08:22 UTCVendor advisory
  56. 2026-08-09 19:36 UTCEG score recompute
  57. 2026-08-09 19:36 UTCVendor advisory
  58. 2026-08-09 13:46 UTCEPSS rescore
  59. 2026-08-09 06:49 UTCEG score recompute
  60. 2026-08-09 06:49 UTCVendor advisory
  61. 2026-08-08 16:37 UTCEPSS rescore
  62. 2026-08-08 06:06 UTCVendor advisory
  63. 2026-08-07 17:19 UTCEG score recompute
  64. 2026-08-07 17:19 UTCVendor advisory
  65. 2026-08-06 19:23 UTCEG score recompute
  66. 2026-08-06 19:23 UTCVendor advisory
  67. 2026-08-06 13:46 UTCEPSS rescore
  68. 2026-08-06 01:30 UTCEG score recompute
  69. 2026-08-06 01:30 UTCVendor advisory
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 10:38 UTCEPSS rescore
  73. 2026-08-04 02:33 UTCVendor advisory
  74. 2026-08-03 13:44 UTCVendor advisory
  75. 2026-08-03 12:49 UTCEG score recompute

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 on March 20, 2026, with the most recent update on September 17, 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 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32829?
CVE-2026-32829 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32829?
A fix for CVE-2026-32829 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32829 are linked in the Vendor Advisories panel on this page.

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.