Repository navigation
chore(deps): update the lockfile to clear RustSec advisories - #42
Merged
Merged
Conversation
Cargo.lock moves trino-rust-client from 98b44b0 to 360d73c on stackable-main, which raises zstd from 0.13 to 0.14 and with it zstd-safe to 8.2.0 and zstd-sys to 2.1.2. Those three lines carry RUSTSEC-2026-0391, RUSTSEC-2026-0395 through 0406 and RUSTSEC-2026-0410: use-after-free, double free, out-of-bounds reads and uninitialised memory in the zstd wrapper, and data from an abandoned stream leaking into the next one on a reused context. The remaining advisories need only a plain cargo update, which this lock also carries: rustls 0.23.46 (RUSTSEC-2026-0285, 0346 to 0349), rustls-webpki 0.103.16 (0382), webpki-root-certs 1.0.11 (0383), quinn-proto 0.11.19 (0338 to 0342) and tokio 1.54.1 (0386). The other entries in the diff are the routine point releases a cargo update brings along; cargo tree finds nothing in this crate's graph for the new borsh, indexmap and zlib-rs entries, so they resolve only for features this crate does not enable. cargo audit against the advisory database from 2026-10-27 reports no vulnerabilities on the new lock. The one warning left is RUSTSEC-2024-0436, paste being unmaintained, which has no fixed version and stays ignored in deny.toml. No source changes. Verified with cargo test, the ffi and backend ignored tests, every suite in integration-tests/run-tests.sh on Linux and the same suites on the Windows VM, and pre-commit run --all-files. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 27, 2026
RUSTSEC-2026-0406: Use-after-free when changing a multithreaded context with an unfinished frame
#36
Closed
Closed
Closed
This was referenced Oct 27, 2026
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cargo.lock moves trino-rust-client from 98b44b0 to 360d73c on stackable-main, which raises zstd from 0.13 to 0.14 and with it zstd-safe to 8.2.0 and zstd-sys to 2.1.2. Those three lines carry RUSTSEC-2026-0391, RUSTSEC-2026-0395 through 0406 and RUSTSEC-2026-0410: use-after-free, double free, out-of-bounds reads and uninitialised memory in the zstd wrapper, and data from an abandoned stream leaking into the next one on a reused context.
The remaining advisories need only a plain cargo update, which this lock also carries: rustls 0.23.46 (RUSTSEC-2026-0285, 0346 to 0349), rustls-webpki 0.103.16 (0382), webpki-root-certs 1.0.11 (0383), quinn-proto 0.11.19 (0338 to 0342) and tokio 1.54.1 (0386). The other entries in the diff are the routine point releases a cargo update brings along; cargo tree finds nothing in this crate's graph for the new borsh, indexmap and zlib-rs entries, so they resolve only for features this crate does not enable.
cargo audit against the advisory database from 2026-10-27 reports no vulnerabilities on the new lock. The one warning left is RUSTSEC-2024-0436, paste being unmaintained, which has no fixed version
and stays ignored in deny.toml.
No source changes. Verified with cargo test, the ffi and backend ignored tests, every suite in integration-tests/run-tests.sh on Linux and the same suites on the Windows VM, and pre-commit run --all-files.
CI fix bundled in
The first run of this PR failed in the pre-commit job at "Install cargo-deny and cargo-sort", unrelated to the lock.
taiki-e/install-actionv2.85.8 verifies cargo-sort 2.1.4 against a sha256 that stopped matching when the cargo-sort v2.1.4 release was re-created with new assets on 2026-10-23 (https://github.com/DevinR528/cargo-sort/releases/tag/v2.1.4; install-action's corrected manifest: https://github.com/taiki-e/install-action/commits/main/manifests/cargo-sort.json). The second commit bumps the pin to v2.87.32 inbuild.yaml,security_audit.yamlandrelease.yaml. Only the first of those was failing; the other two move for a single consistent pin.