Skip to content

fix(deps): update rustls, rustls-webpki and webpki-roots for RustSec advisories (LAB-10248) - #21

Merged
27Bslash6 merged 1 commit into
mainfrom
lab-10248-rustls-advisories
Oct 21, 2026
Merged

27Bslash6 merged 1 commit into
mainfrom
lab-10248-rustls-advisories

Conversation

@27Bslash6

Copy link
Copy Markdown
Contributor

The checks job fails cargo-deny's advisories check on main and on every open PR. Six RustSec advisories now cover the locked TLS stack, which reaches ck through cachekit-rs → reqwest → hyper-rustls. This updates the three crates to their fixed versions.

Crate From To Advisories
rustls 0.23.45 0.23.46 RUSTSEC-2026-0346, -0347, -0348, -0349
rustls-webpki 0.103.15 0.103.16 RUSTSEC-2026-0382
webpki-roots 1.0.9 1.0.10 RUSTSEC-2026-0381

Only Cargo.lock changes, from cargo update -p rustls -p rustls-webpki -p webpki-roots. The resolver kept each crate to a Rust 1.85 compatible version, so rust-version is unchanged.

Every CI step passes locally on this commit: cargo deny --all-features check (advisories, bans, licenses and sources ok), the path-dependency check, cargo fmt --check, cargo clippy --locked --all-targets -D warnings, cargo test --locked, the release build with its binary grep, the hit-path bench, and cargo +1.85 check --locked --all-targets. The same cargo deny run on main fails with the six IDs above.

…advisories

cargo-deny fails the advisories check on the locked TLS stack, which
reaches the binary through cachekit-rs -> reqwest -> hyper-rustls:

- rustls 0.23.45 -> 0.23.46: RUSTSEC-2026-0346, -0347, -0348, -0349
- rustls-webpki 0.103.15 -> 0.103.16: RUSTSEC-2026-0382
- webpki-roots 1.0.9 -> 1.0.10: RUSTSEC-2026-0381

Cargo.lock only, from `cargo update -p rustls -p rustls-webpki
-p webpki-roots`. The resolver kept each to a Rust 1.85 compatible
version, so rust-version is unchanged.
@27Bslash6

Copy link
Copy Markdown
Contributor Author

@kody start-review

@27Bslash6
27Bslash6 merged commit 6c44481 into main Oct 21, 2026
5 checks passed
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