Skip to content

fix(security): bump zstd crates to clear RustSec advisories - #204

Draft
GavinRay97 wants to merge 1 commit into
mainfrom
gavin/vuln-dep-updates-2026-11
Draft

GavinRay97 wants to merge 1 commit into
mainfrom
gavin/vuln-dep-updates-2026-11

Conversation

@GavinRay97

Copy link
Copy Markdown
Member

Summary

Bumps the zstd crates in Cargo.lock:

  • zstd → 0.13.4+
  • zstd-safe → 7.4+
  • zstd-sys 2.0.15 → 2.1.3

Clears RUSTSEC-2026-0391 (data from an abandoned stream leaking into the next), -0398 and -0403 (uninitialized memory / bad Vec length in decompression), and -0410. cargo audit: 4 → 0 advisories.

Trivy reported the released v2.1.5 image and Cargo.lock as clean, because these are RustSec-only advisories.

Verification

  • cargo build --locked and cargo test --locked --no-run pass on toolchain 1.94.1.
  • cargo audit: 0 advisories.

This is part of the DDN connector vulnerability sweep for the non-ndc-jdbc connectors. Rust lockfiles are checked with cargo audit against the RustSec advisory DB (as of 2026-11-17), because Trivy's DB misses many RustSec advisories. Once this merges, a new release tag publishes the patched image.

Originating bot: https://prompt.ql.app/project/hasuraql/promptql-playground/thread/3a3bf742-a20b-4003-b350-59948bbd1585

zstd, zstd-safe, zstd-sys (RUSTSEC-2026-0391/0398/0403/0410). cargo audit: 4 -> 0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant