fix: upgrade lz4_flex to 0.11.6, 0.12.1 (CVE-2026-32829)

[orbisai0security]

Summary

Upgrade lz4_flex from 0.11.2 to 0.11.6, 0.12.1 to fix CVE-2026-32829.

Vulnerability

Field	Value
ID	CVE-2026-32829
Severity	HIGH
Scanner	trivy
Rule	CVE-2026-32829
File	frontend/rust-lib/Cargo.lock

Description: lz4_flex: lz4_flex's decompression can leak information from uninitialized memory or reused output buffer

Changes

• frontend/rust-lib/Cargo.toml
• frontend/rust-lib/Cargo.lock

Verification

• Build passes
• Scanner re-scan confirms fix
• LLM code review passed

---

Automated security fix by OrbisAI Security

Summary by Sourcery

Upgrade Rust frontend dependency to address a high-severity lz4_flex vulnerability.

Bug Fixes:

• Resolve CVE-2026-32829 by updating lz4_flex to patched versions in the Rust frontend library.

Build:

• Bump lz4_flex dependency versions in Cargo.toml and refresh Cargo.lock for the frontend Rust library.

[CLAassistant]

All committers have signed the CLA.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Upgrades the Rust dependency lz4_flex in the frontend rust-lib crate to patched versions in both Cargo.toml and Cargo.lock to address CVE-2026-32829, ensuring the lockfile is consistent with the new dependency graph.

File-Level Changes

Change	Details	Files
Bump lz4_flex dependency to secure versions and refresh lockfile.	Update lz4_flex version requirement in the frontend rust-lib Cargo.toml to use patched releases (0.11.6 / 0.12.1). Regenerate or update Cargo.lock entries so that lz4_flex and any transitive dependencies resolve to the new, non-vulnerable versions. Align lockfile metadata (checksums, package sections) with the updated dependency graph to keep builds reproducible.	frontend/rust-lib/Cargo.toml frontend/rust-lib/Cargo.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since both 0.11.6 and 0.12.1 of lz4_flex are now present, double-check whether you can align transitive dependencies to a single compatible major version to avoid maintaining two parallel versions of the same crate.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since both 0.11.6 and 0.12.1 of `lz4_flex` are now present, double-check whether you can align transitive dependencies to a single compatible major version to avoid maintaining two parallel versions of the same crate.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}